EXECLOAD

Authorization

General User

Purpose

Use the EXECLOAD command to load an exec or XEDIT macro into storage and prepare it for execution.

Operands

fn

is the file name of the exec to be loaded.

ft

is the file type of the exec to be loaded.

fm

is the file mode of the exec to be loaded. The default for file mode is an asterisk (*). You must specify fm (or *) if you want to specify an execname and exectype.

execname

is the name to be assigned to the loaded exec. The default is ‘=’, which means the exec's present file name is to be used.

exectype

is the type to be assigned to the loaded exec. The default is ‘=’, which means the exec's present file type is to be used.

Options

User

specifies the storage for the loaded exec is allocated from user free storage. This is the default.

SYstem

specifies the storage for the loaded exec is allocated from nucleus free storage.

Push

specifies the exec is loaded whether an exec by the same name already exists in storage. This loaded exec does not replace the existing exec. Subsequent invocation of this execname and exectype executes the most recently loaded version. Also, a subsequent EXECDROP of this execname and exectype drops the most recently loaded version.

Usage Notes

1. The file name and file type can each be 1-8 characters. The valid characters are A-Z, a-z, 0-9, $, #, @, +, - (hyphen), : (colon), and _ (underscore). The execname and exectype of the execid can also be 1-8 characters. However, the execname and exectype are not limited to the file name and file type character set. The only characters that are not valid within an execname or exectype are: =, *, (, ), and X'FF'.
2. If SET INSTSEG is ON and you attempt to load an exec into storage with the same execname and exectype as a SHARED exec, you must specify the PUSH option.
3. To list the execs in storage and in a CMS installation saved segment, use the EXECMAP command. To remove an exec from storage or to discontinue use of an exec in a CMS installation saved segment, use the EXECDROP command. Use the SET INSTSEG OFF command to discontinue use of all SHARED execs temporarily. To determine the status of a specific exec, use the EXECSTAT command.
4. The amount of storage required to load an exec includes system overhead for the control blocks and I/O buffers required to maintain the exec in storage.
5. In XA and XC virtual machines, you can load a REXX exec or macro above the 16MB line.
6. When an EXEC or XEDIT macro has been EXECLOADed into storage and the EXEC or XEDIT macro is invoked through a CMSCALL on which a FBLOCK is supplied, the high–order bit of the FBLOCK address must be set on in order for the usage count reported by the EXECMAP command to be incremented. For more information on File Block, see z/VM®: REXX/VM Reference.

Messages and Return Codes

• DMS030E File fn ft fm is already active [RC=37]
• DMS070E Invalid parameter parameter [RC=24]
• DMS104S Error nn reading file fn ft fm from disk [RC=31|55|70|76|99|100+nn]
• DMS109S Virtual storage capacity exceeded [RC=104]
• DMS414E Execid execname exectype already in storage [RC=1]
• DMS417E Only EXEC-2 and REXX EXECs are supported as storage resident EXECs [RC=4]
• DMS2521E EXECLOAD cannot be performed on empty file fn ft [RC=88]

The reasons for these messages and their location are: