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>6751E H<strong>CP</strong>6756E<br />

comm<strong>and</strong> to unlock your privilege classes before you try<br />

to change them.<br />

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

explained below.<br />

MESSAGES:<br />

v Device rdev cannot be redefined because it is the<br />

SYSRES volume.<br />

v Device rdev cannot be redefined because it is the<br />

parm disk volume.<br />

v Device rdev cannot be redefined because it is the<br />

F<strong>CP</strong> device associated with the SCSI SYSRES<br />

device.<br />

Explanation: You receive this message during the IPL<br />

process if you included an RDEVICE statement in the<br />

system configuration file to try to redefine characteristics<br />

of one of the following volumes:<br />

v The system residence volume<br />

v The parm disk volume<br />

v The F<strong>CP</strong> device associated with the SCSI SYSRES<br />

device.<br />

In all cases, the device that the statement is trying to<br />

redefine has already been initialized.<br />

<strong>System</strong> Action: <strong>CP</strong> does not change the device<br />

definition; the IPL process continues normally.<br />

User Response: Edit the system configuration file<br />

before the next IPL. You can include RDEVICE<br />

statements that define the system residence <strong>and</strong> parm<br />

disk volumes as TYPE DASD <strong>and</strong> specify whether they<br />

are shared, but you cannot use RDEVICE statements to<br />

specify anything else about the system residence <strong>and</strong><br />

parm disk volumes. You can include an RDEVICE<br />

statement that defines the F<strong>CP</strong> device associated with<br />

the SCSI SYSRES device as TYPE F<strong>CP</strong> <strong>and</strong> specify<br />

that it is sensed, but you cannot use the RDEVICE<br />

statement to specify anything else about the F<strong>CP</strong><br />

device.<br />

H<strong>CP</strong>6752A Enter password for userid (it will not<br />

appear when typed):<br />

Explanation: You issued a SET PRIVCLASS<br />

comm<strong>and</strong> to unlock the privilege class settings for your<br />

own user ID. You must enter your logon password for<br />

the comm<strong>and</strong> to take effect.<br />

<strong>System</strong> Action: <strong>CP</strong> puts up a <strong>CP</strong> READ <strong>and</strong> waits for<br />

you to issue your logon password. If you enter the<br />

correct password, <strong>CP</strong> unlocks your privilege classes. If<br />

you enter an incorrect password, <strong>CP</strong> issues message<br />

6753, <strong>and</strong> your privilege classes remain locked.<br />

User Response: Enter your logon password.<br />

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

H<strong>CP</strong>6753I An unexpected I/O event occurred.<br />

Explanation: The system detected that an unexpected<br />

I/O event occurred.<br />

<strong>System</strong> Action: The event is ignored <strong>and</strong> system<br />

operation continues.<br />

User Response: None.<br />

H<strong>CP</strong>6754E Comm<strong>and</strong> combination may not be<br />

issued by a disconnected user.<br />

Explanation: A program running in a disconnected<br />

virtual machine issued a <strong>CP</strong> SET PRIVCLASS<br />

comm<strong>and</strong> to unlock the virtual machine’s own privilege<br />

classes. This message appears on the spooled console<br />

of the comm<strong>and</strong> issuer.<br />

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

operation continues.<br />

User Response: Correct the program running in the<br />

disconnected virtual machine so that it does not issue<br />

the <strong>CP</strong> SET PRIVCLASS * UNLOCK comm<strong>and</strong>.<br />

H<strong>CP</strong>6755E User userid currently logged on --<br />

request terminated.<br />

Explanation: You issued a <strong>CP</strong> XSPOOL XLISTADD or<br />

<strong>CP</strong> XSPOOL XLISTDEL comm<strong>and</strong> for a user who is<br />

logged on. Only users who are not logged on may be<br />

added to or deleted from the XSPOOL exclusion lists.<br />

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

operation continues.<br />

User Response: Have the user log off, <strong>and</strong> reissue<br />

the comm<strong>and</strong> before he or she logs back on.<br />

H<strong>CP</strong>6756E Userid pattern not allowed for<br />

{XLISTADD | XLISTDEL}.<br />

Explanation: You tried to use a <strong>CP</strong> XSPOOL<br />

XLISTADD or <strong>CP</strong> XSPOOL XLISTDEL comm<strong>and</strong> to add<br />

a user ID pattern to the input or output exclusion list, or<br />

to delete a user ID pattern from one of them. <strong>CP</strong> only<br />

accepts specific user IDs with these comm<strong>and</strong>s.<br />

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

operation continues.<br />

User Response: Issue a separate <strong>CP</strong> XSPOOL<br />

XLISTADD or <strong>CP</strong> XSPOOL XLISTDEL comm<strong>and</strong> for<br />

each user ID. Alternatively, before your next IPL, you<br />

can add XSPOOL_XLIST_INPUT <strong>and</strong><br />

XSPOOL_XLIST_OUTPUT statements to the system<br />

configuration file to specify the systems you want on the<br />

input <strong>and</strong> output exclusion lists. <strong>CP</strong> accepts patterns<br />

specified on these statements.

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

Saved successfully!

Ooh no, something went wrong!