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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

H<strong>CP</strong>455I Line rdev not operational; {CC=3|<br />

comm<strong>and</strong> reject|fatal i/o error}<br />

Explanation: The communication line is not<br />

operational for the indicated reason.<br />

<strong>System</strong> Action: The communication line is disabled.<br />

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

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

H<strong>CP</strong>475I Fatal I/O error trying to read directory<br />

from volid [for user userid]<br />

Explanation: The z/<strong>VM</strong> directory that the system is<br />

currently using could not be read because of an<br />

unrecoverable I/O error.<br />

<strong>System</strong> Action: The system tries to continue.<br />

User Response: Reissue the comm<strong>and</strong>. If the<br />

problem persists, contact your system operator or<br />

system support personnel.<br />

Operator Response: Try to rewrite the directory as<br />

soon as possible using the directory program<br />

(DIRECTXA). If the failure still exists after rewriting the<br />

directory, the area may have to be reformatted using<br />

ICKDSF or the <strong>CP</strong>FMTXA utility.<br />

The error recording records contain information on the<br />

unrecoverable read errors.<br />

If the problem persists, after reformatting <strong>and</strong> rewriting<br />

the directory, call your system support personnel.<br />

Programmer Response: If the problem persists,<br />

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

<strong>and</strong> correct the hardware problem.<br />

H<strong>CP</strong>477E Traceid traceid not enabled; incomplete<br />

definition<br />

Explanation: The trace ID specified requires additional<br />

type dependent information before it can be enabled. If<br />

the trace is of type IO, this message may be issued for<br />

two reasons:<br />

v The traceid definition never contained any valid<br />

DEVICE specifications.<br />

v None of the devices specified for the given trace ID<br />

exist.<br />

If the trace is of type DATA, this message may be<br />

issued for two reasons:<br />

v The traceid definition never contained any valid LOC<br />

specifications.<br />

v The traceid definition contains an incomplete IF<br />

statement, possibly missing an ENDIF statement.<br />

<strong>System</strong> Action: The trace ID is not enabled, <strong>and</strong> the<br />

rest of the comm<strong>and</strong> is processed.<br />

User Response: Find the missing information on<br />

traceid using either the TRSOURCE DISPLAY or<br />

H<strong>CP</strong>455I H<strong>CP</strong>482E<br />

QUERY TRSOURCE comm<strong>and</strong>, <strong>and</strong> define the missing<br />

information using the required oper<strong>and</strong>s. Then enter the<br />

TRSOURCE comm<strong>and</strong> again to enable the trace.<br />

If the trace was of type IO, verify all DEVICE oper<strong>and</strong>s<br />

specified exist before attempting to enable again. At<br />

least one of the specified devices should exist. If the<br />

trace was of type DATA, verify all LOC oper<strong>and</strong>s are<br />

specified <strong>and</strong> all IF statements are completed.<br />

H<strong>CP</strong>479E Traceid traceid currently enabled<br />

Explanation: The trace ID for which the comm<strong>and</strong><br />

was invoked has already been enabled <strong>and</strong> cannot be<br />

altered.<br />

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

existing trace definition is not modified.<br />

User Response: Disable the trace ID <strong>and</strong> make the<br />

desired modification.<br />

H<strong>CP</strong>480E AN OPERAND OF THE LOAD<br />

STATEMENT IS MISSING.<br />

Explanation: An oper<strong>and</strong> of the LOAD statement is<br />

missing.<br />

<strong>System</strong> Action: Processing is terminated, <strong>and</strong> control<br />

is returned to the caller with return code of 2 in register<br />

15.<br />

User Response: Refer to z/<strong>VM</strong>: <strong>CP</strong> Planning <strong>and</strong><br />

Administration to determine what the content of the<br />

statement should have been. Correct the missing<br />

oper<strong>and</strong>s in the control statement <strong>and</strong> reissue the<br />

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

H<strong>CP</strong>481E THE LOAD STATEMENT TYPE FIELD IS<br />

INVALID; ONLY “C”, “G”, “P”, OR “U”<br />

IS ALLOWED.<br />

Explanation: The indicator of the type of LOAD<br />

control statement is invalid. It can be only C for<br />

CONTROL, G for POSIXGROUP, P for PROFILE, or U<br />

for USER.<br />

<strong>System</strong> Action: Processing is terminated, <strong>and</strong> control<br />

is returned to the caller with return code 2 in register 15.<br />

User Response: Correct the invalid oper<strong>and</strong> in the<br />

control statement <strong>and</strong> reissue the DIRECTXA comm<strong>and</strong>.<br />

H<strong>CP</strong>482E THE FORMAT OF AN OPERAND ON<br />

THE LOAD STATEMENT IS INVALID -<br />

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

Explanation: The indicated oper<strong>and</strong> on the LOAD<br />

control statement is the wrong length or format.<br />

<strong>System</strong> Action: Processing is terminated, <strong>and</strong> control<br />

is returned to the caller with return code 2 in register 15.<br />

User Response: Correct the invalid oper<strong>and</strong> in the<br />

control statement <strong>and</strong> reissue the DIRECTXA comm<strong>and</strong>.<br />

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

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

Saved successfully!

Ooh no, something went wrong!