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.

H<strong>CP</strong>2770I H<strong>CP</strong>2773I<br />

supplied, directing <strong>CP</strong> to reject any<br />

<strong>CP</strong>XUNLOAD request for the load ID.<br />

requested load ID is still in use by a system service<br />

At least one external entry point associated<br />

with the load ID is in use by <strong>CP</strong> for one of the<br />

following reasons:<br />

v It is being used as a message repository.<br />

v It is being used for a TRSOURCE trace<br />

entry.<br />

request was denied by the control entry point<br />

<strong>CP</strong> called the entry point name, <strong>and</strong> the entry<br />

point returned a nonzero return code. Any<br />

nonzero return code directs <strong>CP</strong> to reject the<br />

request.<br />

<strong>System</strong> Action: <strong>CP</strong> rejects the <strong>CP</strong>XUNLOAD<br />

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

User Response: Your action depends on the reason<br />

specified:<br />

requested load ID was not found<br />

Enter the request again, making sure to specify<br />

the correct load ID. Use QUERY <strong>CP</strong>XLOAD to<br />

help find the load ID that you want.<br />

requested load ID was loaded as PERMANENT<br />

<strong>CP</strong> may not perform the unload. You must<br />

re-IPL your system to remove the external<br />

entry points associated with the load ID. If you<br />

need to be able to unload the external entry<br />

points, then you must specify TEMPORARY<br />

when <strong>CP</strong>XLOAD is requested.<br />

requested load ID is still in use by a system service<br />

After terminating usage (by DISASSOCIATE<br />

MESSAGE or by TRSOURCE DROP), you<br />

may enter the request again.<br />

request was denied by the control entry point<br />

Investigate why the entry point rejected the<br />

request.<br />

H<strong>CP</strong>2770I <strong>CP</strong>XUNLOAD for load ID loadid has<br />

been scheduled<br />

Explanation: This is an informational message telling<br />

you that <strong>CP</strong> has accepted your request to unload the<br />

customer-written <strong>CP</strong> routines assigned to load identifier<br />

loadid, but has not completed unloading all of the<br />

routines.<br />

<strong>System</strong> Action: After unloading all the<br />

customer-written <strong>CP</strong> routines, <strong>CP</strong> issues message<br />

H<strong>CP</strong>2771I; system operation continues.<br />

User Response: None.<br />

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

H<strong>CP</strong>2771I <strong>CP</strong>XUNLOAD for load ID loadid has<br />

been completed<br />

Explanation: This is an informational message telling<br />

you that <strong>CP</strong> has finished unloading all the<br />

customer-written <strong>CP</strong> routines assigned to load identifier<br />

loadid.<br />

<strong>System</strong> Action: <strong>CP</strong> displays the message text; system<br />

operation continues.<br />

User Response: None.<br />

H<strong>CP</strong>2772E Relocatable address constant is not 4<br />

bytes long<br />

Explanation: An address constant, requiring address<br />

relocation, was found in the file that you tried to load. All<br />

relocated address values in <strong>CP</strong> must be 4 bytes long.<br />

<strong>System</strong> Action: <strong>CP</strong> rejects the request; system<br />

operation continues.<br />

User Response: Investigate the source code for the<br />

file that you tried to load, looking for any address<br />

constants not 4 bytes long that require relocation. These<br />

would typically be found in DC (Define Constant) or<br />

CCW (Channel Comm<strong>and</strong> Word) assembler statements.<br />

Exp<strong>and</strong> DC addresses to 4 bytes; convert CCW <strong>and</strong><br />

CCW0 statements to CCW1 statements.<br />

H<strong>CP</strong>2773I Entry point name name is unknown at<br />

this time; processing continues<br />

Explanation: This is an informational message that<br />

displays the name of an entry point that <strong>CP</strong> cannot<br />

locate at this time. This entry point is associated with a<br />

<strong>CP</strong> comm<strong>and</strong>, DIAGNOSE code, <strong>CP</strong> exit point, or local<br />

message repository.<br />

This message can occur during <strong>CP</strong> initialization as the<br />

result of configuration file processing. If the <strong>CP</strong>XLOAD<br />

statement is specified in the configuration file without<br />

the NODELAY oper<strong>and</strong>, then the load of the code<br />

containing the entry point may be delayed until after the<br />

statement that needs the entry point (such as<br />

ASSOCIATE EXIT) is processed.<br />

<strong>System</strong> Action: <strong>CP</strong> displays the message text; system<br />

operation continues.<br />

User Response: If you misspelled the name of the<br />

entry point, use one of the following comm<strong>and</strong>s to<br />

correct the mistake:<br />

v ASSOCIATE EXIT<br />

v ASSOCIATE MESSAGES or MSGS<br />

v DISASSOCIATE<br />

v MODIFY COMMAND or CMD<br />

v MODIFY DIAGNOSE<br />

If the entry point name is correct, make it known to <strong>CP</strong><br />

by using the <strong>CP</strong>XLOAD comm<strong>and</strong> to load the file (or<br />

files) that contain the specified entry point name.

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

Saved successfully!

Ooh no, something went wrong!