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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
H<strong>CP</strong>6707E H<strong>CP</strong>6710E<br />
v Invalid instruction - string<br />
v Invalid I/O priority - priority<br />
v Invalid portname - portname<br />
v Invalid switchname - switchname<br />
v Invalid VLAN id - vlanid<br />
Explanation: You will receive a version of this<br />
message in one of two cases:<br />
v You entered a comm<strong>and</strong> that specified an option that<br />
was not valid.<br />
v <strong>CP</strong> is processing a system configuration file that<br />
contains a statement with an option that is not valid.<br />
<strong>System</strong> Action: <strong>CP</strong> rejects the comm<strong>and</strong> or<br />
statement; system operation continues.<br />
User Response: If the error is in a comm<strong>and</strong>, correct<br />
the comm<strong>and</strong> <strong>and</strong> enter it again. If the error is in a<br />
statement in the system configuration file, correct the<br />
statement. If the error is serious, re-IPL; if not, you can<br />
wait until the next IPL.<br />
Important Note<br />
If you received a message about an invalid<br />
comm<strong>and</strong>, subcomm<strong>and</strong>, or entry point name <strong>and</strong><br />
you did not use the <strong>CP</strong> DEFINE COMMAND,<br />
CMD comm<strong>and</strong>, or configuration file statement,<br />
then an internal error has occurred. Contact your<br />
<strong>IBM</strong> software support for programming support.<br />
H<strong>CP</strong>6707E Statement exceeded maximum length<br />
of 4000 on record nnnnnnnn in file fn ft.<br />
Explanation: You IPLed or entered the <strong>CP</strong> REFRESH<br />
LOGOINFO comm<strong>and</strong>, <strong>and</strong> the system is trying to use a<br />
configuration file containing a statement that either has<br />
records that are too long or has too many continuations.<br />
When it is processing configuration files, <strong>CP</strong> only<br />
accepts records that are 4000 or fewer characters long.<br />
<strong>System</strong> Action: <strong>CP</strong> aborts processing of the<br />
configuration file.<br />
User Response: If the error is in the system<br />
configuration file, correct the statement. If it is a serious<br />
error, re-IPL; 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>6708I Insufficient contiguous storage to<br />
allocate the SCMBK area, nnnnnnnnnn<br />
pages were requested.<br />
Explanation: You IPLed, <strong>and</strong> <strong>CP</strong> cannot obtain<br />
sufficient storage for subchannel measurement blocks<br />
(SCMBKs).<br />
<strong>System</strong> Action: IPLing continues; the channel<br />
subsystem will not make any device measurements.<br />
388 z/<strong>VM</strong>: <strong>System</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong> — <strong>CP</strong><br />
Programs such as the Performance Toolkit for <strong>VM</strong> will<br />
find no performance data for individual devices.<br />
User Response: Increase the amount of storage<br />
available to your machine.<br />
H<strong>CP</strong>6709E Too many items specified - token<br />
Explanation: An option was repeated more than the<br />
allowable maximum number of times.<br />
<strong>System</strong> Action: <strong>CP</strong> does not execute the comm<strong>and</strong> or<br />
ignores the statement.<br />
User Response: If the error is in the system<br />
configuration file, correct the statement. If it is a serious<br />
error, re-IPL; 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 <strong>CP</strong> REFRESH LOGOINFO<br />
comm<strong>and</strong> to ensure that <strong>CP</strong> has the correct logo<br />
information.<br />
H<strong>CP</strong>6710E The variations of this message are<br />
explained below.<br />
MESSAGES:<br />
v Imbedding file fn ft would cause an imbed loop --<br />
statement ignored.<br />
v File fn ft does not exist <strong>and</strong> cannot be imbedded.<br />
v -SYSTEM- cannot be resolved because system ID<br />
is undefined -- file fn ft cannot be imbedded.<br />
v Including file fn ft would cause an INCLUDE loop<br />
-- statement ignored<br />
Explanation:<br />
v You included an IMBED statement in the system<br />
configuration file. This statement specifies a file that<br />
contains another IMBED statement. The statement in<br />
this file may specify the system configuration file<br />
itself, or it may specify another file that contains yet<br />
another IMBED statement. Somewhere in the chain<br />
of files, one of the IMBED statements specifies either<br />
the system configuration file or another file that has<br />
already been imbedded, thus causing an infinite loop.<br />
For example, SYSTEM CONFIG A imbeds LOCAL<br />
CONFIG A, which imbeds SYSTEM CONFIG A.<br />
v An IMBED statement in the system configuration file<br />
imbeds a file that cannot be found on the parm disk<br />
accessed at IPL time.<br />
v An IMBED statement has a file name or file type of<br />
-SYSTEM-. The system name has not been identified<br />
in H<strong>CP</strong>SYS or in the system configuration file.<br />
v You specified an INCLUDE directive in the system<br />
configuration file. This directive specifies a file that<br />
contains another INCLUDE directive or an IMBED<br />
statement. Somewhere in the chain of files, one of<br />
the INCLUDE directives or IMBED statements<br />
specifies either the system configuration file or<br />
another file that has already been imbedded, thus<br />
causing an infinite (or “include”) loop.