Installation
In the context of a new installation or the reconfiguration of a Server Unit, the model lock diskette read in by customer support stores the model and hardware characteristics on the Server Unit. These characteristics are: the model ID, the globally unique IDs of the installed CPUs, the Server Unit’s nominal MP level, the number of spare CPUs available (only for SUs /390) and the number of extra CPUs as agreed to in the contract.
IPL
During startup the CPUs are put in to operation in accordance with the number of multiprocessors (ATTACHED, ONLINE, NORMAL).
Extra CPUs remain detached in BS2000 (DETACHED, OFFLINE, EXTRA).
spare CPUs also remain detached (DETACHED, OFFLINE, SPARE) if the model is a model with two or more CPUs. The spare CPU is attached (DETACHED, ONLINE, SPARE) for models with only one CPU.
IPL specifies a CPU for normal operations using the firmware, and it is checked by the BS2000 software. The state of the CPU is displayed with the SHOW-DEVICE-CONFIGURATION CLASS=*CPU command.
CPU failure
When a CPU fails (MFA=Malfunction Alert, MCKI=Machine Check Interrupt) on an SU /390, BS2000 detaches the defective CPU (DETACHED, OFFLINE, ERROR) and simultaneously attaches a spare CPU that is ready for operation.
The following messages (which are also sent to the service center as a teleservice call) are output when this is done:
ETMRK48 CPU (&01) DETACHED BY SYSTEM
ETMRK20 CPU (&01) ATTACHED BY SYSTEM
After a MFA the detached CPU is locked for any following “IPL/Power on Reset” or IMPL. BS2000 does not display it anymore after the next IPL or IMPL. Only after the CPU is repaired or exchanged by the service (the entire server must be offline to do this) can the CPU be declared to be available via an SVP frame.
When a CPU fails for a different reason (e.g. a CPU loop), detaching the CPU normally has no effect on the next startup (DETACHED, ONLINE, NORMAL). A spare CPU is not attached in this case.
Attaching and detaching extra CPUs
In accordance with the contractual duration of usage, extra CPUs can be attached by the operator for a limited time. On BS2000 systems this is done using the expanded operands of the ATTACH-DEVICE and DETACH-DEVICE commands:
/ATTACH-DEVICE UNIT=*EXTRA-CPU(CPU-IDENTIFIER=<x-string 2..2>/*ALL/*ANY)
| All detached extra CPUs are attached. |
Additional messages when the commands are being processed (asynchronous, no command return codes):
ETMRK58 EXTRA-CPU (&00) ATTACHED ETMRK5A ALL EXTRA-CPU'S ALREADY ATTACHED ETMRK5E OBJECT EXTRA-CPU NOT EXISTING ON THIS HARDWARE
The extra CPUs are detached in a similar fashion:
/DETACH-DEVICE UNIT=*EXTRA-CPU(CPU-IDENTIFIER=<x-string 2..2>/*ALL/*ANY)
| All attached extra CPUs are detached |
Additional messages when the commands are being processed (asynchronous, no command return codes):
ETMRK59 EXTRA-CPU (&00) DETACHED ETMRK5B ALL EXTRA-CPU'S ALREADY DETACHED ETMRK5E OBJECT EXTRA-CPU NOT EXISTING ON THIS HARDWARE
The attaching and detaching is recorded in the special SYS.RESLOG.<server-id> log file (see the “Diagnostics Handbook” [14]).
An operable spare CPU is also automatically attached when an extra CPU fails (for SUs /390 only).
The use of the extra services terminates once the BS2000 session terminates or when it terminates abnormally. The extra CPUs are added again explicitly when a new session is started.
Expanding the output of the information commands
Example: Information on CPUs (SU /390 with 2 extra CPUs and 1 spare CPU
/SHOW-DEVICE-CONFIGURATION UNIT=*SELECT(CLASS=*CENTRAL-PROC) MNEM UN-CLASS UN-TYPE CONF-STATE POOL/SIDE 00 CPU SU700-30 ATTACH /ON NORMAL 01 CPU SU700-30 ATTACH /ON NORMAL 02 CPU SU700-30 ATTACH /ON NORMAL 03 CPU SU700-30 ATTACH /ON EXTRA 04 CPU SU700-30 DET(EX)/OFF EXTRA 05 CPU SU700-30 DET(EX)/OFF SPARE