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.

found on a minidisk accessed by <strong>CP</strong>, or the member<br />

name that was requested was not found within the file<br />

that was found.<br />

<strong>System</strong> Action: Processing of the requested function<br />

stops. <strong>System</strong> operation continues.<br />

User Response: Use the <strong>CP</strong> QUERY <strong>CP</strong>DISK<br />

comm<strong>and</strong> for a list of disks accessed by <strong>CP</strong>. Use the<br />

<strong>CP</strong> <strong>CP</strong>LISTFILE comm<strong>and</strong> to obtain a list of files <strong>and</strong><br />

members on <strong>CP</strong>-accessed disks.<br />

If the message indicates that the member name was not<br />

found, check the file. In order for a file to contain<br />

members, it must be a CMS partitioned data set (PDS),<br />

such as a TXTLIB. Also, note that the file type in that<br />

case is expected to have LIB as the last three<br />

characters.<br />

If the error occurs as a result of the <strong>CP</strong>XLOAD<br />

configuration file statement, ensure that the files are<br />

available on a disk that <strong>CP</strong> has accessed when the<br />

<strong>CP</strong>XLOAD statement is processed. See the z/<strong>VM</strong>: <strong>CP</strong><br />

Planning <strong>and</strong> Administration for details.<br />

H<strong>CP</strong>6704E Missing {<strong>CP</strong>U model number|<strong>CP</strong>U<br />

serial number|system ID|token} at end<br />

of line.<br />

Explanation: A requested option or oper<strong>and</strong> was<br />

missing. The comm<strong>and</strong> or statement ended prematurely.<br />

<strong>System</strong> Action: <strong>CP</strong> does not execute the comm<strong>and</strong> or<br />

process the statement; system operation continues.<br />

User Response: Correct the error <strong>and</strong> enter the<br />

comm<strong>and</strong> again. If the error was in a statement, tell <strong>CP</strong><br />

to process the configuration file again.<br />

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

explained below.<br />

MESSAGES:<br />

v Comment starting on line nnnnnnnn in fn ft was<br />

never completed.<br />

v Statement starting on line nnnnnnnn in fn ft was<br />

continued past end of file.<br />

Explanation: You IPLed the system or entered the<br />

REFRESH LOGOINFO comm<strong>and</strong>, <strong>and</strong> the system is<br />

trying to use a configuration file that contains the<br />

beginning of a comment without the end of one, or has<br />

a comma after the last statement.<br />

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

ignores the last statement if it has a comma after it.<br />

User Response: The system operator or system<br />

programmer must decide if the error is in the system<br />

configuration file. If it is a serious error, re-IPL;<br />

otherwise, you can wait until the next IPL.<br />

If the error is in the logo configuration file, correct the<br />

error <strong>and</strong> enter the REFRESH LOGOINFO comm<strong>and</strong> to<br />

ensure that <strong>CP</strong> has the correct logo information.<br />

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

explained below.<br />

MESSAGES:<br />

v Invalid file name - string<br />

v Invalid file type - string<br />

v Invalid address range - string<br />

v Invalid string - string<br />

v Invalid character - string<br />

v Invalid number - string<br />

v Invalid model number - string<br />

v Invalid time zone offset - string<br />

v Invalid date - string<br />

v Invalid time - string<br />

v Invalid time zone ID - string<br />

v Invalid form name - string<br />

v Invalid spool file class - string<br />

v Invalid identifier - string<br />

v Invalid volume label - string<br />

v Invalid device address - string<br />

v Invalid RDEV - string. RDEV not initialized<br />

v Invalid cylinder number - string<br />

v Invalid track number - string<br />

v Invalid number of records - string<br />

v Invalid record length - string<br />

v Invalid system name - string<br />

v Invalid system alias - string<br />

v Invalid file mode - string<br />

v Invalid line number - string<br />

v Invalid disk mode - string<br />

v Invalid screen size - string<br />

v Invalid privilege classes - string<br />

v Invalid access mode - string<br />

v Invalid group name - string<br />

v Invalid account ID - string<br />

v Invalid <strong>CP</strong>U model number - string<br />

v Invalid <strong>CP</strong>U serial number - string<br />

v Invalid routine name - string<br />

v Invalid comm<strong>and</strong> name - string<br />

v Invalid subcomm<strong>and</strong> name - string<br />

v Invalid entry point name - string<br />

v Invalid Diagnose code - string<br />

v Invalid <strong>CP</strong> Exit number - string<br />

v Invalid file member name - string<br />

v Invalid alias name - string<br />

v Invalid <strong>IBM</strong> class - string<br />

v Invalid product - string<br />

v Invalid product state - string<br />

v Invalid exit number - string<br />

H<strong>CP</strong>6704E H<strong>CP</strong>6706E<br />

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

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

Saved successfully!

Ooh no, something went wrong!