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>6532I H<strong>CP</strong>6540I<br />

operating system will accept comm<strong>and</strong>s entered from<br />

the system console.<br />

H<strong>CP</strong>6532I There is no {priority|non-priority}<br />

message currently outst<strong>and</strong>ing with<br />

message number nnnn assigned to it.<br />

Explanation: This message is entered in response to<br />

a VDELETE comm<strong>and</strong> entered by the virtual machine<br />

console operator. The service processor, being<br />

simulated by z/<strong>VM</strong>, has no message of the designated<br />

type with message number nnn on its queue of<br />

messages that it has intercepted from the operating<br />

system running in your virtual machine. The message<br />

may have been deleted at the request of the operating<br />

system running in your virtual machine.<br />

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

Operator Response: Message numbers are assigned<br />

to messages, for deletion purposes, by the QUERY<br />

<strong>VM</strong>SG/P<strong>VM</strong>SG comm<strong>and</strong>. Reenter the QUERY<br />

<strong>VM</strong>SG/P<strong>VM</strong>SG comm<strong>and</strong> followed by the VDELETE<br />

comm<strong>and</strong> specifying the message number for the<br />

message to be deleted.<br />

H<strong>CP</strong>6533A Following is a priority message<br />

received by the service processor -<br />

use the VINPUT comm<strong>and</strong> to respond:<br />

Explanation: This message is displayed on your<br />

virtual machine operator’s console when <strong>CP</strong> intercepts a<br />

priority message that was sent by the operating system<br />

running in your virtual machine to the service processor<br />

(simulated by <strong>CP</strong>) for display on the system console<br />

attached to the hardware processor. <strong>CP</strong> displays this<br />

<strong>CP</strong> message before displaying the intercepted operating<br />

system priority message on your virtual machine<br />

operator’s console so that you will know that the<br />

operating system message is a priority message that<br />

must be responded to immediately.<br />

<strong>System</strong> Action: <strong>CP</strong> places the virtual machine<br />

operator’s console in <strong>CP</strong> READ mode so that you may<br />

respond to the operating system message that follows.<br />

User Response: Enter the appropriate operating<br />

system comm<strong>and</strong> using the <strong>CP</strong> VINPUT comm<strong>and</strong> so<br />

that z/<strong>VM</strong> will route the specified operating system<br />

comm<strong>and</strong> to the operating system running in your virtual<br />

machine as though the comm<strong>and</strong> originated from the<br />

service processor (which provides support for the<br />

system console attached to the hardware processor).<br />

Operator Response: None.<br />

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

H<strong>CP</strong>6535E A paging error occurred reading a<br />

pageable page table from {DASD rdev<br />

volume device identifier|exp<strong>and</strong>ed<br />

storage}. <strong>System</strong> resources (up to 256<br />

{DASD paging slots|exp<strong>and</strong>ed storage<br />

blocks <strong>and</strong>/or DASD paging slots})<br />

may have been lost.<br />

Explanation: The error was caused by bringing the<br />

page into real storage from DASD or Exp<strong>and</strong>ed<br />

Storage. This is a probable hardware error.<br />

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

User Response: Re-IPL the virtual machine.<br />

Operator Response: If the error is from DASD read,<br />

examine the console messages or LOGREC, or both,<br />

for the DASD involved.<br />

If the error is due to PGIN from XSTORE, examine the<br />

console messages.<br />

Programmer Response: Contact your <strong>IBM</strong> Support<br />

Center.<br />

H<strong>CP</strong>6536E There are two variations of this message<br />

explained below<br />

Explanation: The link address xxx exceeds two<br />

digits - A DEFINE CU or MODIFY CU comm<strong>and</strong> was<br />

issued <strong>and</strong> the link address specified contained more<br />

than two digits. The processor only supports link<br />

addresses of two digits or less.<br />

<strong>System</strong> Action: The comm<strong>and</strong> failed. <strong>System</strong><br />

operation continues.<br />

User Response: Re-issue the comm<strong>and</strong> specifying a<br />

link address of one or two digits.<br />

Explanation: Number of link addresses does not<br />

match the number of channel paths - A DEFINE CU<br />

or MODIFY CU comm<strong>and</strong> was issued <strong>and</strong> the number<br />

of link addresses specified did not equal the number of<br />

channel paths specified.<br />

<strong>System</strong> Action: The comm<strong>and</strong> failed. <strong>System</strong><br />

operation continues.<br />

User Response: When link addresses are specified<br />

on the DEFINE CU or MODIFY CU comm<strong>and</strong>s, provide<br />

a link address for each channel path identifier (CHPID)<br />

specified in the same order. Re-issue the comm<strong>and</strong><br />

specifying the same number of link addresses <strong>and</strong><br />

channel paths.<br />

H<strong>CP</strong>6540I The I/O configuration is not in a valid<br />

state; HCD recovery is required.<br />

Explanation: During system re-initialization, it was<br />

determined that HCD is in control of the hardware I/O<br />

configuration <strong>and</strong> that the current hardware I/O<br />

configuration is in an invalid state that does not match a<br />

known configuration defined in a production IODF. HCD

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

Saved successfully!

Ooh no, something went wrong!