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.

H<strong>CP</strong>6843E H<strong>CP</strong>6846E<br />

H<strong>CP</strong>6843E All versions of the comm<strong>and</strong> must<br />

have the same logon value<br />

Explanation: <strong>CP</strong> rejected the request to define a new<br />

version of an existing <strong>CP</strong> comm<strong>and</strong> (same comm<strong>and</strong><br />

name, different <strong>IBM</strong> class) because the new version did<br />

not have the same BEFORE_LOGON value as the<br />

existing <strong>CP</strong> comm<strong>and</strong>. You can define several versions<br />

of a comm<strong>and</strong> with any combination of AFTER_LOGON<br />

<strong>and</strong> ANYTIME values. However, when you define one<br />

version of a comm<strong>and</strong> with the BEFORE_LOGON<br />

oper<strong>and</strong>, you must specify the BEFORE_LOGON<br />

oper<strong>and</strong> on all other versions of that comm<strong>and</strong>.<br />

<strong>System</strong> Action: <strong>CP</strong> does not define the new version;<br />

system operation continues.<br />

User Response: Define the new version again, <strong>and</strong><br />

specify the same BEFORE_LOGON value as the<br />

existing comm<strong>and</strong>.<br />

Important Note<br />

If you did not use the <strong>CP</strong> DEFINE COMMAND<br />

comm<strong>and</strong> or configuration file statement to define<br />

the new version, then an internal error has<br />

occurred. Contact your <strong>IBM</strong> software support for<br />

programming support.<br />

H<strong>CP</strong>6844E All versions of the comm<strong>and</strong> must<br />

have the same {PROC value|entry point<br />

name|entry point address|minimum<br />

abbreviation|SILENT setting}<br />

Explanation: <strong>CP</strong> rejected the request to define a new<br />

version of an existing <strong>CP</strong> comm<strong>and</strong> (same comm<strong>and</strong><br />

name, different <strong>IBM</strong> class) because the new version did<br />

not have the same PROC value, entry point name, entry<br />

point address, minimum abbreviation, or SILENT setting<br />

as the existing <strong>CP</strong> comm<strong>and</strong>. These respective values<br />

must be identical in all versions of a <strong>CP</strong> comm<strong>and</strong>.<br />

<strong>System</strong> Action: <strong>CP</strong> does not define the new version;<br />

system operation continues.<br />

User Response: Define the new version again, <strong>and</strong><br />

either specify the same PROC value, entry point name,<br />

entry point address, minimum abbreviation, or SILENT<br />

setting as the existing <strong>CP</strong> comm<strong>and</strong>, or do not specify<br />

these values <strong>and</strong> let <strong>CP</strong> copy them from the existing<br />

versions of the comm<strong>and</strong>.<br />

Important Note<br />

If you did not use the <strong>CP</strong> DEFINE COMMAND<br />

comm<strong>and</strong> or configuration file statement to define<br />

the new version, then an internal error has<br />

occurred. Contact your <strong>IBM</strong> software support for<br />

programming support.<br />

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

H<strong>CP</strong>6845E You must specify {an entry point<br />

name|a privilege class|an <strong>IBM</strong> class}<br />

[other than 0]}<br />

Explanation: <strong>CP</strong> rejected the request to define a new<br />

<strong>CP</strong> comm<strong>and</strong> because you did not specify some<br />

required information about the new comm<strong>and</strong>. When<br />

you define a new <strong>CP</strong> comm<strong>and</strong>, you must specify the<br />

name of the entry point containing the code to process<br />

the new comm<strong>and</strong>, the privilege class or classes of the<br />

new comm<strong>and</strong> (which cannot be 0), <strong>and</strong> the <strong>IBM</strong> class<br />

of the new comm<strong>and</strong> (which cannot be 0). The only<br />

exception to this rule is if you are defining a new alias<br />

to an existing <strong>CP</strong> comm<strong>and</strong>. In this case, the alias uses<br />

the same entry point, privilege classes, <strong>and</strong> <strong>IBM</strong> class<br />

of the existing comm<strong>and</strong>. You are not defining an alias,<br />

so you must specify the missing information.<br />

<strong>System</strong> Action: <strong>CP</strong> does not define the new<br />

comm<strong>and</strong>; system operation continues.<br />

User Response: Define the comm<strong>and</strong> again, <strong>and</strong><br />

specify the entry point name, privilege class, or <strong>IBM</strong><br />

class that you omitted in your last attempt to define the<br />

new <strong>CP</strong> comm<strong>and</strong>.<br />

Important Note<br />

If you did not use the <strong>CP</strong> DEFINE COMMAND<br />

comm<strong>and</strong> or configuration file statement to define<br />

the new <strong>CP</strong> comm<strong>and</strong>, then an internal error has<br />

occurred. Contact your <strong>IBM</strong> software support for<br />

programming support.<br />

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

explained below.<br />

MESSAGES:<br />

v Requested entry point name is not an external<br />

label in the nucleus<br />

v Requested entry point name is not at the address<br />

indicated<br />

Explanation: <strong>CP</strong> rejected the request to define a new<br />

<strong>CP</strong> comm<strong>and</strong> because there was a problem locating the<br />

specified entry point name. If you receive the first<br />

message, <strong>CP</strong> cannot locate your entry point name<br />

anywhere in the <strong>CP</strong> nucleus. If you receive the second<br />

message, an internal error has occurred while defining<br />

the new <strong>CP</strong> comm<strong>and</strong>. <strong>CP</strong> rejected the new comm<strong>and</strong><br />

because an entry point name <strong>and</strong> address were passed<br />

to <strong>CP</strong> during invocation, <strong>and</strong> <strong>CP</strong> located the entry point<br />

name, but the entry point address in the <strong>CP</strong> nucleus did<br />

not match the address that was passed during<br />

invocation.<br />

<strong>System</strong> Action: <strong>CP</strong> does not define the new<br />

comm<strong>and</strong>; system operation continues.<br />

User Response: For the first message, define the<br />

comm<strong>and</strong> again, <strong>and</strong> ensure that you specify an entry<br />

point within the <strong>CP</strong> nucleus. For the second message,

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

Saved successfully!

Ooh no, something went wrong!