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>6158E Your access to this address space has<br />

been revoked.<br />

Explanation: Your access to the address space<br />

expired while it was being used. The address space<br />

was originally specified in a DISPLAY/DUMP/STORE<br />

comm<strong>and</strong> using the ASIT or SPACE oper<strong>and</strong>.<br />

<strong>System</strong> Action: The system continues to run, but the<br />

comm<strong>and</strong> entered by the user is stopped while partially<br />

complete.<br />

User Response: Contact the owner of the address<br />

space to reestablish your access. Clean up the partially<br />

completed comm<strong>and</strong> if necessary.<br />

H<strong>CP</strong>6159E Address space may not be specified<br />

following the {PSWA/FROM/RANGE<br />

options|BRANCH oper<strong>and</strong>} of the<br />

TRACE comm<strong>and</strong> while in ESA/XC<br />

mode<br />

Explanation: An address space oper<strong>and</strong> is not valid<br />

following the options: PSWA, FROM, or RANGE, or<br />

following the BRANCH oper<strong>and</strong> of the TRACE<br />

comm<strong>and</strong> when the virtual machine is in ESA/XC mode.<br />

<strong>System</strong> Action: The comm<strong>and</strong> does not run. <strong>System</strong><br />

operation continues.<br />

User Response: Enter the comm<strong>and</strong> again, correctly<br />

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

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

explained below.<br />

MESSAGES:<br />

v token1 was not expected. ‘DL’ or ‘IF’ was<br />

expected.<br />

v token1 was not expected. A datalink string was<br />

expected.<br />

v token1 was not expected. A Boolean operator was<br />

expected.<br />

v token1 was not expected. A datalink string or<br />

constant was expected.<br />

v token1 was not expected. ‘THEN’ was expected.<br />

v token1 was not expected. ‘DL’, ‘IF’, ‘ELSE’, or<br />

‘ENDIF’ was expected.<br />

v token1 was not expected. ‘DL’, ‘IF’, or ‘ENDIF’ was<br />

expected.<br />

Explanation: The TRSOURCE TYPE DATA comm<strong>and</strong><br />

processor unexpectedly encountered token1.<br />

<strong>System</strong> Action: The trace ID is not updated with any<br />

of the datalink information from this comm<strong>and</strong>.<br />

User Response: Enter the TRSOURCE comm<strong>and</strong><br />

again with the required oper<strong>and</strong>s. The QUERY<br />

TRSOURCE comm<strong>and</strong> can be used to determine the<br />

current state of the trace ID.<br />

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

explained below.<br />

MESSAGES:<br />

H<strong>CP</strong>6158E H<strong>CP</strong>6163E<br />

v Constant definition incorrect: Length too long.<br />

v Constant definition incorrect: Missing quote.<br />

v Constant definition incorrect: Null string<br />

specified.<br />

v Constant definition incorrect: Non-hexadecimal<br />

data specified.<br />

v Constant definition incorrect: Data after second<br />

quote.<br />

v Constant definition incorrect: Odd number of<br />

hexadecimal digits specified.<br />

Explanation: The TRSOURCE TYPE DATA comm<strong>and</strong><br />

processor found an error while processing a constant<br />

definition.<br />

<strong>System</strong> Action: The trace ID is not updated with any<br />

of the datalink information from this comm<strong>and</strong>.<br />

User Response: Enter the TRSOURCE comm<strong>and</strong><br />

again with the required constant specified correctly.<br />

H<strong>CP</strong>6162E Maximum nesting depth of IF<br />

statement exceeded.<br />

Explanation: The TRSOURCE TYPE DATA comm<strong>and</strong><br />

processor encountered an IF oper<strong>and</strong> while processing<br />

the comm<strong>and</strong>. This new IF would cause the nesting<br />

depth of IF statements within this trace ID to exceed the<br />

maximum depth allowed by <strong>CP</strong>, which is 16.<br />

<strong>System</strong> Action: The trace ID is not updated with any<br />

of the datalink information from this comm<strong>and</strong>.<br />

User Response: Restructure the conditional datalink<br />

so it can achieve the desired filtering by satisifying less<br />

conditions. It will be necessary to drop this trace ID <strong>and</strong><br />

start again. Enter the TRSOURCE comm<strong>and</strong> again with<br />

the required oper<strong>and</strong>s. The QUERY TRSOURCE<br />

comm<strong>and</strong> can be used to determine the current state of<br />

the trace ID.<br />

H<strong>CP</strong>6163E Internal error during comm<strong>and</strong><br />

processing: module + offset<br />

Explanation: The TRSOURCE TYPE DATA comm<strong>and</strong><br />

processor encountered an error while processing this<br />

comm<strong>and</strong>. This message can only occur when<br />

abnormal conditions are detected.<br />

<strong>System</strong> Action: The trace is not updated with any of<br />

the datalink information from this comm<strong>and</strong>.<br />

User Response: Enter the comm<strong>and</strong> again. The<br />

QUERY TRSOURCE can be used to display the trace<br />

information that has already been defined. It may be<br />

necessary to drop this trace <strong>and</strong> redefine it. If this<br />

message occurs when redefining the trace, call the <strong>IBM</strong><br />

Support Center. They will need to know the text of the<br />

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

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

Saved successfully!

Ooh no, something went wrong!