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>6877I The system operator ID has been<br />

changed to userid.<br />

Explanation: You see this message when all of the<br />

following are true:<br />

v you are logging off as the primary system operator<br />

v the alternate operator IDs have been specified in the<br />

system configuration file<br />

v either the default system operator ID or one of the<br />

alternates automatically replaced you as the system<br />

operator.<br />

<strong>System</strong> Action: <strong>CP</strong> changed the operator ID to the<br />

one displayed in the message. <strong>System</strong> operation<br />

continues.<br />

User Response: None.<br />

H<strong>CP</strong>6878E AMODE/RMODE VALUES CONFLICT<br />

Explanation: You ran the H<strong>CP</strong>LDR utility, <strong>and</strong> you<br />

specified values for the AMODE <strong>and</strong> RMODE keywords<br />

that conflict with each other. You cannot specify an<br />

AMODE of 24 with an RMODE of ANY.<br />

<strong>System</strong> Action: <strong>CP</strong> rejects the comm<strong>and</strong>; system<br />

operation continues.<br />

User Response: Correct the value of AMODE or<br />

RMODE <strong>and</strong> issue the H<strong>CP</strong>LDR comm<strong>and</strong> again.<br />

H<strong>CP</strong>6879E THE LENGTH OF THE MODULE TO BE<br />

GENERATED IS NON-POSITIVE<br />

Explanation: You ran the H<strong>CP</strong>LDR utility, <strong>and</strong> you<br />

specified a value on the FROM keyword equal to or<br />

larger than the one you specified on the TO keyword.<br />

<strong>System</strong> Action: <strong>CP</strong> rejects the comm<strong>and</strong>; system<br />

operation continues.<br />

User Response: Correct <strong>and</strong> reissue the comm<strong>and</strong>.<br />

H<strong>CP</strong>6881E userid vdev not in <strong>CP</strong> directory.<br />

Explanation: You issued a SHUTDOWN REIPL<br />

comm<strong>and</strong> with the MDISK option, <strong>and</strong> the minidisk you<br />

specified does not exist in the <strong>CP</strong> directory.<br />

<strong>System</strong> Action: <strong>CP</strong> ignores the comm<strong>and</strong>; normal<br />

processing continues.<br />

User Response: You can look at entries in the user<br />

directory to find out which minidisks you can specify on<br />

a SHUTDOWN REIPL comm<strong>and</strong>.<br />

H<strong>CP</strong>6882E userid vdev is not a minidisk.<br />

Explanation: You issued a SHUTDOWN REIPL<br />

comm<strong>and</strong> with the MDISK option, <strong>and</strong> the virtual device<br />

you specified is not a minidisk.<br />

<strong>System</strong> Action: <strong>CP</strong> ignores the comm<strong>and</strong>; system<br />

operation continues.<br />

User Response: You can look at entries in the user<br />

directory to find out which minidisks you can specify on<br />

a SHUTDOWN REIPL comm<strong>and</strong>.<br />

H<strong>CP</strong>6883E userid vdev not accessible -- volume<br />

volid not mounted.<br />

Explanation: You issued a <strong>CP</strong> SHUTDOWN REIPL<br />

comm<strong>and</strong> with the MDISK option, <strong>and</strong> the minidisk you<br />

specified resides on a volume that is not mounted.<br />

<strong>System</strong> Action: <strong>CP</strong> ignores the comm<strong>and</strong>; system<br />

operation continues.<br />

User Response: Bring the volume containing the<br />

minidisk online <strong>and</strong> attach it to the system, or issue<br />

another <strong>CP</strong> SHUTDOWN REIPL comm<strong>and</strong> specifying<br />

another minidisk on a volume that is already mounted.<br />

You can find out whether a volume is mounted by<br />

issuing a <strong>CP</strong> QUERY DASD volid comm<strong>and</strong>.<br />

H<strong>CP</strong>6884E The variations of this message are<br />

explained below.<br />

MESSAGES:<br />

v Unable to access re-IPL minidisk because no free<br />

access slot is available.<br />

v Unable to access re-IPL minidisk because of an<br />

I/O error.<br />

v Unable to access re-IPL minidisk because the<br />

disk is not CMS formatted.<br />

Explanation: When you issue a <strong>CP</strong> SHUTDOWN<br />

REIPL comm<strong>and</strong>, <strong>CP</strong> looks for a minidisk that contains<br />

the information that it needs to re-IPL. This minidisk<br />

may be the original minidisk that <strong>CP</strong> used for its most<br />

recent IPL, or it may be another minidisk that you<br />

specified on the <strong>CP</strong> SHUTDOWN REIPL comm<strong>and</strong>. The<br />

versions of this message tell you that <strong>CP</strong> has<br />

encountered one of the following errors when it tried to<br />

access the minidisk:<br />

v <strong>CP</strong> already has a minidisk accessed in each of the<br />

26 available slots.<br />

v There is an I/O error.<br />

H<strong>CP</strong>6877I H<strong>CP</strong>6884E<br />

v The minidisk that <strong>CP</strong> tried to access was not<br />

CMS-formatted.<br />

You receive a version of this message only if <strong>CP</strong> was<br />

originally loaded from a module.<br />

<strong>System</strong> Action: <strong>CP</strong> ignores the SHUTDOWN<br />

comm<strong>and</strong>; system operation continues.<br />

User Response: If you received the first version of<br />

this message, issue a <strong>CP</strong>RELEASE comm<strong>and</strong> to free at<br />

least one access slot before you issue another<br />

SHUTDOWN REIPL comm<strong>and</strong>. If you received the<br />

second version, issue HYPERSWAP RESUME on the<br />

device <strong>and</strong> reissue the SHUTDOWN comm<strong>and</strong>. If you<br />

still receive a message that there is an I/O error, try to<br />

access the disk from a regular CMS id. If I/O errors<br />

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

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

Saved successfully!

Ooh no, something went wrong!