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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

H<strong>CP</strong>448E H<strong>CP</strong>454I<br />

H<strong>CP</strong>448E <strong>System</strong> name not quiesced{.<br />

Outst<strong>and</strong>ing I/O on device rdev.| due to<br />

an outst<strong>and</strong>ing external interrupt.}<br />

Explanation: You did not quiesce the indicated system<br />

in order to allow the save to continue.<br />

<strong>System</strong> Action: <strong>CP</strong> halts processing of the SAVESEG<br />

or SAVESYS comm<strong>and</strong> <strong>and</strong> does not save the NSS or<br />

saved segment skeleton file.<br />

Programmer Response: Ensure that the NSS or<br />

saved segment does not have any outst<strong>and</strong>ing I/O or<br />

external interrupts. Then issue the comm<strong>and</strong> again.<br />

H<strong>CP</strong>449E Your userid is not authorized to IPL<br />

system name.<br />

Explanation: You issued an IPL specifying restricted<br />

NSS name without the necessary authorization in the<br />

<strong>CP</strong> directory. If an external security manager (ESM) is<br />

installed on your system, you may receive this message<br />

if you are not authorized to IPL the specified system.<br />

<strong>System</strong> Action: The comm<strong>and</strong> is not executed;<br />

system operation continues.<br />

Programmer Response: Obtain the authorization to<br />

access the restricted NSS from your system<br />

administrator.<br />

H<strong>CP</strong>450W <strong>CP</strong> entered; disabled wait PSW psw<br />

Explanation: The virtual machine loaded a disabled<br />

wait PSW, identified by psw.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues. The<br />

virtual machine enters console function mode. If the<br />

virtual machine was running disconnected, it is logged<br />

off the system.<br />

User Response: This message may have been<br />

preceded by an explanatory message from the<br />

operating system running in your virtual machine. If it is<br />

not, examine the PSW portion of the message. To<br />

interpret the wait state code in the PSW, refer to the<br />

section on wait states of the corresponding manual for<br />

the system you were running in your virtual machine.<br />

Take the specified corrective action, then re-IPL the<br />

virtual system again.<br />

The following paragraph is an explanation of a possible<br />

wait state situation for the CMS environment. It is not<br />

the only wait state that can be sent to a user. It is just<br />

an example of what the wait state might look like.<br />

If you were running CMS, <strong>and</strong> you received this<br />

message with the PSW ‘00060000 00000070’, then<br />

CMS received a virtual machine check. Re-IPL CMS<br />

<strong>and</strong> try again.<br />

Programmer Response: Examine the PSW portion of<br />

the message. Ensure that the program running in the<br />

virtual machine has a valid load PSW (LPSW). If not,<br />

176 z/<strong>VM</strong>: <strong>System</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong> — <strong>CP</strong><br />

determine why the PSW loaded was not masked for<br />

interrupts.<br />

H<strong>CP</strong>452I <strong>CP</strong> entered; external interrupt loop<br />

Explanation: While h<strong>and</strong>ling an external interrupt, the<br />

user’s virtual machine external new PSW is enabled for<br />

an external interrupt condition that will not be cleared<br />

upon acceptance (for example, the timer is not expected<br />

to contain a negative value). It is possible to receive an<br />

interrupt condition from the <strong>CP</strong>U timer <strong>and</strong> the<br />

time-of-day (TOD) clock comparator that produces this<br />

loop.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues. The<br />

virtual machine enters <strong>CP</strong> comm<strong>and</strong> mode.<br />

User Response: To continue, IPL the virtual system<br />

again.<br />

Programmer Response: Determine why the external<br />

interrupt new PSW is enabled for an interrupt condition<br />

that will not be cleared upon acceptance (that is, the<br />

timer is not expected to contain a negative value).<br />

H<strong>CP</strong>453W <strong>CP</strong> entered; program interrupt loop<br />

Explanation: A program interrupt occurred at the<br />

address specified in the virtual program new PSW.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues. If no<br />

virtual <strong>CP</strong>U remains operational, the program interrupt<br />

is reflected to the virtual machine, the virtual <strong>CP</strong>U is<br />

placed in hard stop, <strong>and</strong> the user enters console<br />

function mode. If the virtual machine was running<br />

disconnected, it is logged off the system.<br />

User Response: After correcting the error, reissue the<br />

IPL comm<strong>and</strong>.<br />

Programmer Response: To determine the reason for<br />

the loop, examine the program-check information in<br />

page zero of your virtual storage. If this error occurred<br />

immediately after the IPL comm<strong>and</strong>, the problem may<br />

be that you are trying to run a 370 guest in XA mode.<br />

z/<strong>VM</strong> no longer supports 370 mode; try using the 370<br />

Accommodation Facility.<br />

H<strong>CP</strong>454I Line rdev disabled<br />

Explanation: The communication line is disabled as a<br />

result of I/O errors. See message H<strong>CP</strong>455I for reason<br />

of error.<br />

<strong>System</strong> Action: None.<br />

Operator Response: Check the line for any possible<br />

problems, <strong>and</strong> then try to enable the line.

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

Saved successfully!

Ooh no, something went wrong!