z/VM: CP Commands and Utilities Reference - z/VM - IBM

CPXLOAD
Responses
3. The customer-written CP routines that you are loading must be on a disk that
CP has access to when the load operation is performed. If you have a
CPXLOAD statement in your system configuration file that specifies the
NODELAY operand, the customer-written CP routines must be on the parm
disk because the minidisks specified on CP_ACCESS statements are not
available until the end of the initialization process. If your CPXLOAD statement
specifies the DELAY operand, the customer-written CP routines can be a file
on any disk, as long as you have specified a CP_ACCESS statement for that
disk in your system configuration file.
4. You can specify run-time and load operands on either the CPXLOAD
command or the OPTIONS directive, or both. However, if you specify options
on both and those options conflict, CP uses the options from the CPXLOAD
command. For example, suppose you specify PERMANENT on the OPTIONS
directive and TEMPORARY on the CPXLOAD command, CP will load the CP
routines as temporary. For more information about the OPTIONS directive and
several other directives, see the z/VM: CP Exit Customization book.
5. To assign entry points and external symbols to an exit point and to enable or
disable that exit point, use the ASSOCIATE EXIT command (page 18).
6. To assign an external symbol to a local message repository, use the
ASSOCIATE MESSAGES or MSGS command (page 23).
7. To display information about customer-written CP routines loaded by the
CPXLOAD command, use the QUERY CPXLOAD command (page 751).
8. To display information about external symbols you may have loaded, use the
LOCATE SYMBOL command (page 557).
9. To remove CPXLOADed files from CP’s system execution space:
a. Use the DISASSOCIATE command (page 274) to revoke all entry point
and external symbol assignments made with the ASSOCIATE EXIT,
MESSAGES, or MSGS commands or configuration file statements
b. Use the CPXUNLOAD command (page 107) to unload the
customer-written CP routines.
For more information about the ASSOCIATE EXIT, MESSAGES, or MSGS
statements, see the z/VM: CP Planning and Administration book.
10. For more information about loading customer-written CP routines into CP’s
system execution space, about run-time and load operands, and about
CPXLOAD directives, see the z/VM: CP Exit Customization book.
11. CPXLOAD provides the ability to load executable code, message repositories,
and data modules dynamically. Only compiled files may be loaded. These
compiled files would be the TEXT file output from the assembler or from the
CMS GENMSG command.
Response 1:
104 z/VM: CP Commands and Utilities Reference
To permanently load a multiprocessor capable abend text deck, enter the following:
cpxload abend text * mp control kaos permanent
Loaded as identifier 7
Ready;
Note that CP assigns a load identifier (load ID) to the loaded CP routines. Please
make a note of this number. If you ever want to unload these CP routines (using
the CPXUNLOAD command), you will need to specify the load ID that CP assigned.
If you do not know the load ID, use the ALL operand of the QUERY CPXLOAD