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: Comm<strong>and</strong> execution terminates <strong>and</strong><br />

system operation continues.<br />

User Response: Fix the problem associated with the<br />

specified return code (nnnn) <strong>and</strong> enter the SET<br />

IOCDS_ACTIVE comm<strong>and</strong> again. For more information<br />

about the return code, see the z/<strong>VM</strong>: I/O Configuration<br />

book.<br />

H<strong>CP</strong>6813E Query CHPIDs comm<strong>and</strong> failed with<br />

return code nn<br />

Explanation: You used the QUERY CHPIDS<br />

comm<strong>and</strong> to display all 256 of the machine’s channel<br />

paths <strong>and</strong> their physical status, but the comm<strong>and</strong> failed<br />

with the specified return code (nnnn).<br />

<strong>System</strong> Action: Comm<strong>and</strong> execution terminates <strong>and</strong><br />

system operation continues.<br />

User Response: Fix the problem associated with the<br />

specified return code (nnnn) <strong>and</strong> enter the QUERY<br />

CHPIDS comm<strong>and</strong> again. For more information about<br />

the return code, see the z/<strong>VM</strong>: I/O Configuration book.<br />

H<strong>CP</strong>6814E Comm<strong>and</strong> is not valid on this<br />

processor<br />

Explanation: A user tried to execute the Query<br />

CHPIDS comm<strong>and</strong> <strong>and</strong> the comm<strong>and</strong> is not supported<br />

on this processor.<br />

<strong>System</strong> Action: Comm<strong>and</strong> execution terminates <strong>and</strong><br />

system operation continues.<br />

User Response: None.<br />

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

explained below.<br />

MESSAGES:<br />

v Cannot find configuration token in the channel<br />

subsystem<br />

Explanation: The system has not been set up to<br />

utilize Dynamic I/O configuration as no channel<br />

subsystem token has been found.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues, but<br />

dynamic I/O configuration is not allowed.<br />

User Response: Follow the procedure outline in the<br />

z/<strong>VM</strong>: I/O Configuration book on how to set up your<br />

system for Dynamic I/O. This will place a channel<br />

subsystem token into the hardware.<br />

v Comm<strong>and</strong> failed in channel subsystem.<br />

Explanation: The system has been defined to enable<br />

Dynamic I/O Configuration, but an error occurred<br />

when doing so.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues, but<br />

dynamic I/O configuration is not allowed.<br />

User Response: Enter the Set DYNAMIC_IO<br />

comm<strong>and</strong> to see if the error persists. If it does,<br />

contact your system support staff.<br />

v Cannot find configuration token in the system<br />

Explanation: A user entered a dynamic I/O<br />

comm<strong>and</strong> on a system with the dynamic I/O support<br />

enabled, but no configuration token was found in the<br />

system.<br />

<strong>System</strong> Action: The dynamic I/O comm<strong>and</strong> is not<br />

executed.<br />

User Response: Contact your system programmer.<br />

<strong>System</strong> Programmer Response: Verify that the<br />

configuration is still intact <strong>and</strong> matches the active<br />

IOCDS. Examine responses from the last dynamic<br />

changes <strong>and</strong> make sure that they all completed<br />

successfully. If everything appears satisfactory, the<br />

tokens stored in the system common area might have<br />

been overlaid. Try entering the SET DYNAMIC_IO<br />

OFF comm<strong>and</strong> to disable dynamic I/O support. Then<br />

enter the SET DYNAMIC_IO ON comm<strong>and</strong> to<br />

reinitialize the configuration tokens. You might have<br />

to re-IPL the system to solve the problem.<br />

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

explained below.<br />

MESSAGES:<br />

v Dynamic I/O changes are not allowed on this<br />

system<br />

Explanation: No dynamic changes are allowed on<br />

the system because the system does not support<br />

Dynamic I/O configuration.<br />

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

User Response: None.<br />

H<strong>CP</strong>6813E H<strong>CP</strong>6816E<br />

v Dynamic I/O changes are not allowed for device<br />

rdev<br />

Explanation: Dynamic changes are not allowed for<br />

the device as the system has been configured to<br />

disallow any dynamic I/O operation on this device.<br />

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

User Response: If you want to allow dynamic I/O<br />

operations on this device, you must remove it from<br />

the DEVICES NOTDYNamic I/O statement.<br />

v Dynamic I/O changes are not allowed because<br />

LPAR information is not available<br />

Explanation: Dynamic I/O configuration is not<br />

enabled because the system cannot determine the<br />

LPAR definitions.<br />

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

User Response: Contact your system support staff.<br />

v Dynamic I/O changes are not allowed because the<br />

configuration token is not a valid <strong>VM</strong> token<br />

Explanation: A user entered the SET DYNAMIC I/O<br />

ON comm<strong>and</strong> or coded the FEATURES ENABLE<br />

DYNAMIC I/O statement in the system configuration<br />

file. The configuration token found in the channel<br />

subsystem while trying to enable the dynamic I/O<br />

support on the system is not a valid <strong>VM</strong> token.<br />

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

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

Saved successfully!

Ooh no, something went wrong!