27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SHUTDOWN<br />

Responses<br />

c. The new <strong>CP</strong> module must contain the same version of the checkpoint<br />

(H<strong>CP</strong>CKP or H<strong>CP</strong>CKS) <strong>and</strong> warmstart (H<strong>CP</strong>WRM or H<strong>CP</strong>WRS) modules.<br />

d. Any <strong>CP</strong> system volumes that are shared between the old <strong>and</strong> the new<br />

system must have the same position in the <strong>CP</strong>_Owned statement in the<br />

system configuration file.<br />

Otherwise the automatic warmstart may fail <strong>and</strong> a hardware IPL with a FORCE<br />

start must be performed.<br />

6. When a SHUTDOWN is issued, the trace data for all active DEFERIO traces<br />

will not be written.<br />

7. All IPL parameters used with the IPLPARMS option will remain in effect until<br />

they are changed with a subsequent SHUTDOWN REIPL comm<strong>and</strong> that<br />

specifies the IPLPARMS parameter, or the <strong>CP</strong> nucleus is shut down, or a SET<br />

IPLPARMS is issued.<br />

8. If the REIPL option is used, some I/O subsystem features may not be available<br />

if the system that is brought up on the re-IPL supports a superset of the<br />

features supported by the system that was shut down. A full I/O reset is<br />

necessary to support all the features. This can be performed only by using the<br />

Load function on the processor’s hardware console. For example, the Parallel<br />

Access Volumes feature of the 2105 DASD Subsystem may not be available on<br />

re-IPL if the system that was shut down did not support that feature.<br />

9. If none of the WITHIN, BY, <strong>and</strong> IMMEDIATE options are specified, <strong>and</strong> if the<br />

default signal timeout interval is set, it is added to the <strong>CP</strong> shutdown interval <strong>and</strong><br />

the result is used to delay the shutdown <strong>and</strong> give guests an opportunity to<br />

terminate. Refer to “SET SIGNAL” on page 1388 <strong>and</strong> “SET SHUTDOWNTIME”<br />

on page 1387 for additional information about this behavior.<br />

Response 1:<br />

System shutdown may be delayed for up to interval seconds<br />

is displayed when the comm<strong>and</strong> is accepted <strong>and</strong> there are guests that require time<br />

to shut down. If a user other than the primary system operator issues the<br />

SHUTDOWN comm<strong>and</strong>, this response is sent to both the comm<strong>and</strong> issuer <strong>and</strong> the<br />

primary system operator.<br />

Response 2:<br />

SYSTEM SHUTDOWN STARTED<br />

is displayed when the comm<strong>and</strong> is accepted <strong>and</strong> termination processing is in<br />

progress. If a Class A user other than the primary system operator issues the<br />

SHUTDOWN comm<strong>and</strong>, this response is sent to both the comm<strong>and</strong> issuer <strong>and</strong> the<br />

primary system operator.<br />

Response 3:<br />

1436 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

STARTING SYSTEM SHUTDOWN STEP name - description<br />

is displayed for each step of the shutdown process as it proceeds. Each message<br />

identifies the name of the step <strong>and</strong> a description of its function. On a 3270 terminal,<br />

these messages are displayed on the top line of the screen, always showing the<br />

last step that was initiated. On the system console (SYSC) device, the messages<br />

are displayed one after another in line mode.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!