28.12.2012 Views

z/VM: System Messages and Codes Š CP - z/VM - IBM

z/VM: System Messages and Codes Š CP - z/VM - IBM

z/VM: System Messages and Codes Š CP - 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.

H<strong>CP</strong>9204I <strong>System</strong> recovery failed during a forced<br />

start because the block requested is<br />

beyond the checkpoint area.<br />

Explanation: During FORCE start processing, an<br />

EREP, accounting, or system message block was<br />

requested outside the system checkpoint area.<br />

<strong>System</strong> Action: Processing of the EREP, accounting,<br />

or system records ends, <strong>and</strong> the records are lost. The<br />

system continues by restoring system spool <strong>and</strong> data<br />

files.<br />

Operator Response: Contact your system<br />

programmer.<br />

H<strong>CP</strong>9205A The variations of this message are<br />

explained below.<br />

MESSAGES:<br />

v Invalid warm start data encountered. No files<br />

have been deleted yet. To change to a force start,<br />

enter FORCE. To stop processing, enter STOP.<br />

Explanation: The operator has specified a warm<br />

start, <strong>and</strong> warm start data that is not valid was<br />

encountered.<br />

<strong>System</strong> Action: Wait for operator response.<br />

Operator Response: The operator should enter<br />

FORCE if a force start is desired. Otherwise, the<br />

operator should enter STOP to stop processing.<br />

v Checkpoint data is not valid. <strong>System</strong> Data file<br />

recovery data may not be valid. Continuation of<br />

the system IPL could result in the loss of system<br />

data files. To continue COLD start <strong>and</strong> attempt to<br />

recover system data files, enter GO. To stop<br />

processing, enter STOP.<br />

Explanation: The data in the checkpoint area is not<br />

valid. It is possible the warm start data used to<br />

recover system data files is also not valid. This may<br />

result in the loss of system data files.<br />

Operator Response:<br />

– Enter STOP if you wish to stop initialization <strong>and</strong><br />

preserve the previous state of the spooling<br />

system.<br />

– Enter GO to continue initialization. The system<br />

attempts to read the warm start data <strong>and</strong> recover<br />

system data files.<br />

H<strong>CP</strong>9210W SYSTEM TERMINATION COMPLETE;<br />

ISSUE A SYSTEM RESET LOAD TO<br />

RESTART<br />

Explanation: The system termination process has<br />

completed. The system will not restart automatically<br />

because <strong>CP</strong> was unable to terminate an active file load<br />

from the processor controller into main store.<br />

If <strong>CP</strong> is unable to stop the processor controller from<br />

loading a file into main store, the system cannot be<br />

allowed to restart automatically. To restart the system,<br />

the operator must perform a system reset load from the<br />

hardware console. The hardware system reset operation<br />

will terminate the file load, thus allowing <strong>CP</strong> to IPL<br />

without fear of a possible storage overlay from the<br />

processor controller.<br />

<strong>System</strong> Action: The system enters a wait state<br />

(wait-state code = 9210).<br />

User Response: None.<br />

Operator Response: Manually re-IPL the system by<br />

performing a system reset load from the hardware<br />

service console.<br />

Programmer Response: None.<br />

H<strong>CP</strong>9225I SYSTEM RECOVERY FAILURE;<br />

CHECKPOINT AREA FULL<br />

Explanation: The area that the checkpoint information<br />

is kept in cannot accept any more data (the cylinders<br />

(CKD/ECKD devices) or pages (FBA devices) are full.<br />

One reason why checkpoint area cylinders may be full<br />

is a large number of accounting, EREP, <strong>and</strong> symptom<br />

records could be included in the data checkpointed in<br />

those cylinders. Normally these records are retrieved by<br />

virtual machines identified in SYSTEM CONFIG or<br />

H<strong>CP</strong>SYS, but if those virtual machines are not actively<br />

retrieving the records, the records will accumulate.<br />

<strong>System</strong> Action: <strong>CP</strong> aborts checkpoint processing.<br />

If SHUTDOWN was entered:<br />

The system stops.<br />

If SHUTDOWN REIPL was entered:<br />

The system continues <strong>and</strong> then restarts.<br />

Message H<strong>CP</strong>904E is displayed <strong>and</strong> the user<br />

is prompted to change to a FORCE start. All<br />

accounting, EREP, <strong>and</strong> symptom records are<br />

lost.<br />

Operator Response: Contact your system<br />

programmer or the <strong>IBM</strong> Support Center for assistance.<br />

You may need to allocate more checkpoint cylinders<br />

(CKD/ECKD) or pages (FBA). To restart, IPL the system<br />

<strong>and</strong> specify a FORCE start.<br />

H<strong>CP</strong>9250E SYSTEM DUMP FAILURE; NO DUMP<br />

DEVICE AVAILABLE<br />

Explanation: The system was unable to take an<br />

abend dump because there was no device available to<br />

dump to. If a dump was previously specified, it was not<br />

operational. The system was also unable to locate a<br />

printer to dump to.<br />

<strong>System</strong> Action: No dump is taken. The system<br />

continues the system termination process.<br />

User Response: None.<br />

H<strong>CP</strong>9204I H<strong>CP</strong>9250E<br />

Chapter 3. <strong>System</strong> <strong>Messages</strong> 463

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

Saved successfully!

Ooh no, something went wrong!