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.

<strong>System</strong> Action: <strong>CP</strong> ignores the IMBED statement or<br />

INCLUDE directive; system operation continues.<br />

User Response: Edit the system configuration file so<br />

that the IMBED statement or INCLUDE directive<br />

contains a valid file name <strong>and</strong> file type. If you received<br />

the third version of this message, make sure that your<br />

SYSTEM_IDENTIFIER or<br />

SYSTEM_IDENTIFIER_DEFAULT statement is at the<br />

beginning of your configuration file. IPL again.<br />

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

explained below.<br />

MESSAGES:<br />

v Duplicate volume identifier nnnnnn specified --<br />

statement ignored.<br />

v Slot nnn already contains volume nnnnnn --<br />

statement ignored.<br />

v Duplicate routine name nnnnnnnn specified --<br />

statement ignored.<br />

Explanation: You used a <strong>CP</strong>_OWNED,<br />

USER_VOLUME_LIST, XLINK_VOLUME_INCLUDE, or<br />

XLINK_VOLUME_EXCLUDE statement in the system to<br />

specify a volume ID that was already specified on<br />

another such statement, or you entered slot numbers<br />

already specified on another <strong>CP</strong>_OWNED,<br />

XLINK_SYSTEM_INCLUDE, or XSPOOL_SYSTEM<br />

statement in the system configuration file. These<br />

statements can be specified only once per slot in the<br />

list.<br />

For the duplicate routine name format, you used a<br />

<strong>CP</strong>ADDON_INITIALIZE_ROUTINES statement in the<br />

system to specify a routine name that was already<br />

specified on another such statement.<br />

<strong>System</strong> Action: <strong>CP</strong> ignores the statement; system<br />

operation continues.<br />

User Response: Correct the statements in the<br />

configuration file. If the incorrect statements have<br />

caused a serious error, re-IPL; otherwise, you can wait<br />

until the next IPL.<br />

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

explained below.<br />

MESSAGES:<br />

v Translate table file fn ft does not exist or cannot<br />

be opened -- statement ignored.<br />

v Error encountered while attempting to read<br />

records from translation table file fn ft -- file<br />

ignored.<br />

v Token token in translation table file fn ft has an<br />

odd number of characters -- file ignored.<br />

v Invalid hexadecimal token token encountered in<br />

translation table file fn ft -- file ignored.<br />

v Translation table file fn ft contained more than 256<br />

hexadecimal characters -- file ignored.<br />

H<strong>CP</strong>6711E H<strong>CP</strong>6713W<br />

v Translation table file fn ft contained less than 256<br />

hexadecimal characters -- file ignored.<br />

v Translation table file fn ft contained an incomplete<br />

comment -- file ignored.<br />

Explanation: An error was encountered on the<br />

TRANSLATE_TABLE statement or in the translation<br />

table file. Errors that might occur are as follows:<br />

v A file specified on the TRANSLATE_TABLE<br />

statement could not be found on the parm disk.<br />

v An error was encountered reading a file specified on<br />

the TRANSLATE_TABLE statement from the parm<br />

disk.<br />

v There were more or fewer than 256 bytes of<br />

hexadecimal data in the translation table file. (<strong>CP</strong><br />

expects to find exactly 256 hexadecimal characters in<br />

the file.)<br />

v A token was encountered in the translation table file<br />

that contained non-hexadecimal characters.<br />

<strong>System</strong> Action: Statement is ignored; system<br />

configuration file processing continues.<br />

User Response: Correct the error <strong>and</strong> IPL again to<br />

put the new translation table into effect.<br />

H<strong>CP</strong>6713E DEVICES statement would cause<br />

SYSRES device to {become<br />

undefined|remain offline at IPL} --<br />

statement ignored.<br />

Explanation: During post-processing of the system<br />

configuration file, results indicate that a DEVICES<br />

statement in the system configuration file would cause<br />

one of the following things to happen:<br />

v The SYSRES device would be deleted from the I/O<br />

configuration.<br />

v The system residence volume would remain offline.<br />

<strong>System</strong> Action: <strong>CP</strong> ignores the DEVICES statement’s<br />

request.<br />

User Response: Remove the SYSRES device number<br />

from the DEVICES statement so that <strong>CP</strong> does not issue<br />

this error message at each IPL.<br />

H<strong>CP</strong>6713W DEVICES statement would cause<br />

SYSRES device to {become<br />

undefined|remain offline at IPL} --<br />

statement ignored.<br />

Explanation: The SYSRES device was found in either<br />

the DEVICES NOTACCEPTED or the OFFLINE_AT_IPL<br />

statement. If this statement was processed, the<br />

SYSRES device would become undefined, or it would<br />

be offline during system initialization <strong>and</strong> operation.<br />

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

DEVICES statement is ignored.<br />

User Response: Correct the DEVICES statement <strong>and</strong><br />

re-IPL the system.<br />

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

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

Saved successfully!

Ooh no, something went wrong!