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.

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

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

Operator Response: Check the system’s<br />

configuration or contact your system support personnel.<br />

H<strong>CP</strong>8204W RESIDENT DEVICE IS NOT A <strong>CP</strong><br />

FORMATTED VOLUME<br />

Explanation: The resident device is not a<br />

<strong>CP</strong>-formatted volume. This can only occur when the<br />

resident device is a DASD.<br />

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

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

Operator Response: Use ICKDSF to format the<br />

resident device before running the H<strong>CP</strong>SADMP EXEC<br />

to create the st<strong>and</strong>-alone dump utility, or contact your<br />

system support personnel.<br />

H<strong>CP</strong>8205W I/O ERROR WHEN WRITING<br />

STAND-ALONE DUMP UTILITY OR I/O<br />

ERROR ON THE IPL DEVICE WHEN<br />

IPLING THE STAND-ALONE DUMP<br />

UTILITY TO TAKE A STAND-ALONE<br />

DUMP.<br />

Explanation: If this wait state is received when writing<br />

the St<strong>and</strong>-Alone Dump Utility, an I/O error occurred on<br />

the resident (or IPL) device.<br />

If this wait state is received when IPLing the<br />

St<strong>and</strong>-Alone Dump Utility to take a St<strong>and</strong>-Alone Dump,<br />

an I/O error occurred on the resident (or IPL) device.<br />

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

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

Operator Response: Contact your system support<br />

personnel.<br />

Programmer Response: An I/O error occurred. If the<br />

real device is a tape, then mount a new tape. Ensure<br />

the tape is not currently assigned to another system. If<br />

the tape is assigned to another system, free the tape<br />

drive <strong>and</strong> make it available for St<strong>and</strong>-Alone Dump. If the<br />

real device is a DASD, verify the format. If the problem<br />

persists, contact your <strong>IBM</strong> Support Center personnel to<br />

diagnose <strong>and</strong> correct the I/O error.<br />

H<strong>CP</strong>8206W VERIFY PATHS TO DUMP DEVICE; A<br />

POTENTIAL CONFIGURATION<br />

CHANGE WAS DETECTED.<br />

Explanation: A reset event occurred on one of the<br />

paths to this device.<br />

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

state (wait state code = 8206).<br />

Operator Response: Verify no configuration changes<br />

have occurred, <strong>and</strong> then rerun the st<strong>and</strong>-alone dump<br />

utility.<br />

H<strong>CP</strong>8204W H<strong>CP</strong>8255E<br />

H<strong>CP</strong>8250E comm<strong>and</strong> REQUIRES A R/W A-DISK<br />

Explanation: The CCLOAD <strong>and</strong> CCDUMP comm<strong>and</strong>s<br />

require R/W DASD space to create files.<br />

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

User Response: Provide an R/W A disk for any user<br />

ID that uses the CCLOAD or CCDUMP comm<strong>and</strong>s.<br />

H<strong>CP</strong>8251E THE CTLR VIRTUAL DEVICE NUMBER<br />

vdev IS INVALID<br />

Explanation: The device number specified as the<br />

CTLR vdev is not a valid hexadecimal value.<br />

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

User Response: Reenter the comm<strong>and</strong> with a correct<br />

device number.<br />

H<strong>CP</strong>8252E CTLR VIRTUAL DEVICE vdev IS<br />

UNDEFINED<br />

Explanation: Before entering the CCLOAD comm<strong>and</strong>,<br />

a real communication controller must be attached (or<br />

dedicated) to the virtual device specified. Either that<br />

was not done, or you specified a different device<br />

number.<br />

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

User Response: Ensure that the CTLR is dedicated or<br />

attached to the user ID <strong>and</strong> that the virtual device is<br />

correctly specified.<br />

H<strong>CP</strong>8253E AN EP LOAD MODULE NAME IS<br />

REQUIRED<br />

Explanation: The name of the EP control program<br />

load module was not specified on the comm<strong>and</strong>.<br />

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

User Response: Reenter the comm<strong>and</strong> <strong>and</strong> specify<br />

the load module name.<br />

H<strong>CP</strong>8254E lmod IS AN INVALID LOAD MODULE<br />

NAME<br />

Explanation: The specified load module name is<br />

longer than 8 characters or not alphanumeric.<br />

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

User Response: Reenter the comm<strong>and</strong> <strong>and</strong> specify<br />

the correct name of the EP control program load<br />

module.<br />

H<strong>CP</strong>8255E THE COMMAND HAS AN INVALID USE<br />

OF “(”<br />

Explanation: Parentheses were used incorrectly in the<br />

comm<strong>and</strong> oper<strong>and</strong>s.<br />

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

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

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

Saved successfully!

Ooh no, something went wrong!