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>6548E H<strong>CP</strong>6554E<br />

<strong>System</strong> Action: The comm<strong>and</strong> is failed <strong>and</strong> system<br />

operation continues.<br />

User Response: Query the device <strong>and</strong> if it is still<br />

offline, issue the comm<strong>and</strong> again.<br />

H<strong>CP</strong>6548E CHPID chpid cannot be brought online<br />

because HCD is in the process of<br />

dynamically changing this CHPID.<br />

Explanation: <strong>CP</strong> is currently processing an HCD<br />

dynamic I/O request, which is affecting the CHPID. The<br />

CHPID must remain in an offline state until the dynamic<br />

I/O request is completed.<br />

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

system operation continues.<br />

User Response: Re-issue the comm<strong>and</strong>.<br />

H<strong>CP</strong>6549E The subchannel for device rdev cannot<br />

be brought online because HCD is in<br />

the process of dynamically changing<br />

this device.<br />

Explanation: <strong>CP</strong> is currently processing an HCD<br />

dynamic I/O request, which is affecting the device. The<br />

subchannel for the device must remain in an offline<br />

state until the dynamic I/O request is completed.<br />

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

system operation continues.<br />

User Response: Re-issue the comm<strong>and</strong>.<br />

H<strong>CP</strong>6550I HCD is currently disabled for hardware<br />

changes.<br />

Explanation: HCD is unable to dynamically change<br />

the hardware I/O configuration because the<br />

configuration token in the active production IODF does<br />

not match the current channel subsystem configuration<br />

token.<br />

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

User Response: In order to enable HCD for dynamic<br />

I/O hardware changes on this system, the active<br />

production IODF must be dynamically changed to a<br />

production IODF that contains a configuration token<br />

matching the current channel subsystem configuration<br />

token.<br />

H<strong>CP</strong>6551I User userid will not be monitored for<br />

the APPLDATA domain because it is<br />

not authorized<br />

Explanation: A MONITOR SAMPLE/EVENT ENABLE<br />

APPLDATA comm<strong>and</strong> was entered, but the user<br />

specified by userid was not authorized. To be eligible for<br />

the APPLDATA domain, the directory entry for this user<br />

ID must contain the statement OPTION APPLMON. This<br />

statement authorizes the user to issue DIAGNOSE code<br />

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

X'DC', which declares/deletes buffers in which<br />

application data is placed.<br />

<strong>System</strong> Action: The user ID specified is not enabled<br />

for the APPLDATA domain.<br />

User Response: Contact your systems programmer to<br />

have the OPTION APPLMON statement coded in your<br />

directory entry.<br />

H<strong>CP</strong>6552E The size of the {event|sample}<br />

configuration area cannot be changed<br />

because {event|sample} monitoring has<br />

already been started.<br />

Explanation: A MONITOR EVENT CONFIG or<br />

MONITOR SAMPLE CONFIG comm<strong>and</strong> has been<br />

entered, but a monitor comm<strong>and</strong> has already been<br />

entered to start that type of monitoring. Therefore, the<br />

number of pages to be reserved for the configuration<br />

records for that type cannot be changed.<br />

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

User Response: If you want to change the size of the<br />

configuration area, the corresponding type of monitoring<br />

must be stopped first. Then you can enter a MONITOR<br />

EVENT (or SAMPLE) CONFIG comm<strong>and</strong> to specify the<br />

number of pages you want reserved for configuration<br />

records, <strong>and</strong> can restart monitoring.<br />

H<strong>CP</strong>6553E value is an invalid size for monitor<br />

{event|sample} CONFIG.<br />

Explanation: The value specified for CONFIG SIZE in<br />

the MONITOR comm<strong>and</strong> is invalid. This message is<br />

generated when one of the following is true:<br />

v A nonnumeric value was specified.<br />

v The CONFIG value is less than the minimum value<br />

required, or greater than the maximum value allowed,<br />

as documented for the MONITOR comm<strong>and</strong>.<br />

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

User Response: Determine the reason why the<br />

specified value is invalid, <strong>and</strong> reenter the desired<br />

comm<strong>and</strong> with a valid value.<br />

H<strong>CP</strong>6554E The MONITOR EVENT START failed<br />

because the event partition size of n<br />

pages is not large enough. At least m<br />

pages are currently required.<br />

Explanation: A MONITOR EVENT START or<br />

MONITOR START comm<strong>and</strong> has been entered to start<br />

event monitoring. The size of the event partition, which<br />

was specified on the comm<strong>and</strong> or defaulted to 50% of<br />

the saved segment, contains only n pages, which is not<br />

enough pages to contain the pages reserved for event<br />

configuration records <strong>and</strong> the minimum number of<br />

pages for event data records (8 pages).<br />

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

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

Saved successfully!

Ooh no, something went wrong!