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>6095I H<strong>CP</strong>6111I<br />

H<strong>CP</strong>6095I User userid is no longer being traced<br />

by trace traceid.<br />

Explanation: The specified user is no longer being<br />

traced, even though the user is still included in the<br />

specified trace. This could occur for several reasons.<br />

The message entered before this message gives the<br />

reason why the user is not traced.<br />

<strong>System</strong> Action: Tracing for the specified user is<br />

discontinued. <strong>System</strong> operation continues. The<br />

remaining users being traced continue to be traced.<br />

User Response: Your response depends upon the<br />

reason why the user is not traced.<br />

If the problem is that there are too many spool files,<br />

purging some spool files should help. If the problem is<br />

because of a soft abend, contact your system<br />

programmer.<br />

To start the entire trace over again, disable <strong>and</strong> then<br />

enable the entire trace, using the TRSOURCE<br />

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

To start tracing just the specific user again, try the<br />

INCLUDE user option of the TRSOURCE comm<strong>and</strong>.<br />

If the user has restricted tracing to traces defined in<br />

BLOCK mode, verify that the tracing mode is correct for<br />

the capabilities of the virtual machine. See the trace<br />

instructions in z/<strong>VM</strong>: Virtual Machine Operation, for<br />

tracing in the virtual machine, <strong>and</strong> follow them.<br />

H<strong>CP</strong>6096I Trace traceid is being disabled.<br />

Explanation: The specified trace is being disabled.<br />

The message issued before this message gives the<br />

reason why this occurred.<br />

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

operation continues.<br />

User Response: Your response depends upon the<br />

reason why the trace is disabled.<br />

If the problem is that there are too many spool files,<br />

purging some spool files should help. If the problem is<br />

because of a soft abend, contact your system<br />

programmer.<br />

To reenable the trace, use the TRSOURCE comm<strong>and</strong><br />

with the ENABLE option.<br />

If the user has restricted tracing to traces defined in<br />

BLOCK mode, verify that the tracing mode is correct for<br />

the capabilities of the virtual machine. See the trace<br />

instructions for tracing in the virtual machine, <strong>and</strong> follow<br />

them.<br />

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

H<strong>CP</strong>6097I User userid has restricted tracing to<br />

traces defined as BLOCK.<br />

Explanation: The specified user ID has issued a<br />

request to <strong>CP</strong> to allow the virtual machine to only be<br />

part of a guest trace that is defined in BLOCK mode.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues. The<br />

message issued after this message will give more<br />

information about the system action.<br />

User Response: None.<br />

H<strong>CP</strong>6098E Traceid traceid cannot be enabled.<br />

Explanation: The specified trace cannot be enabled.<br />

The message issued before this message gives the<br />

reason why the trace is not enabled.<br />

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

operation continues.<br />

User Response: If the user has restricted tracing to<br />

traces defined in BLOCK mode, verify that the tracing<br />

mode is correct for the capabilities of the virtual<br />

machine. See the trace instructions in z/<strong>VM</strong>: Virtual<br />

Machine Operation, for tracing in the virtual machine,<br />

<strong>and</strong> follow them.<br />

H<strong>CP</strong>6099E DEFERIO trace is invalid for a TYPE<br />

GT BLOCK mode trace.<br />

Explanation: A DEFERIO trace cannot be used for a<br />

TYPE GT BLOCK mode trace.<br />

<strong>System</strong> Action: The comm<strong>and</strong> is not executed;<br />

system operation continues.<br />

User Response: If issuing a TRSAVE comm<strong>and</strong>,<br />

reissue the comm<strong>and</strong> without the DEFERIO option. If<br />

issuing a TRSOURCE ID comm<strong>and</strong>, issue TRSOURCE<br />

DROP to delete the ID so that the TRSAVE with the<br />

DEFERIO option is removed.<br />

H<strong>CP</strong>6111I The variations of this message are<br />

explained below.<br />

MESSAGES:<br />

v type rdev THE ERROR WAS DETECTED ON<br />

MACHINE TYPE xxxx-yy; {THE DEVICE IS<br />

OPERATIONAL (LEVEL=n)} {WITH SPARE<br />

PORT(S) AVAILABLE}<br />

v type rdev THE ERROR WAS DETECTED ON<br />

MACHINE TYPE xxxx-yy; {THE DEVICE IS NOT<br />

OPERATIONAL (LEVEL=4)} {WITH SPARE<br />

PORT(S) AVAILABLE}<br />

v type rdev THE ERROR WAS DETECTED ON<br />

MACHINE TYPE xxxx-yy; {OPERATIONAL LEVEL<br />

IS UNKNOWN (LEVEL=5)} {WITH SPARE PORT(S)<br />

AVAILABLE}<br />

v FRUs = cmp1, cmp2, cmp3, cmp4

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

Saved successfully!

Ooh no, something went wrong!