EXECLOAD
EXECLOAD loads an exec into virtual storage.
Operands
- ddn
- specifies the ddname that is read.
- member
- specifies the member of the partitioned dataset that is used.
- name
- specifies a fully qualified RFS file name or the fully qualified PDS name and member.
- MEM
- indicates that a ddname and member name has been specified.
- RFS
- indicates that an RFS file has been specified.
- PDS
- indicates that a partitioned dataset name and member has been specified.
Return codes
- 0
- Normal return
- 1501
- Invalid command
- 1502
- Invalid operand
- 1523
- Error storing EXECLOAD information
- 1525
- Error retrieving EXECLOAD information
- 1530
- Unable to link to CICPDS routine
- 1531
- Error returned from CICPDS routine
- 1532
- Error returned from RFS READ
- 1532
- Error returned from PDS build
- 1547
- GETMAIN error
- 1548
- No client available
- 1599
- Internal error
Example
'EXECLOAD POOL1:\USERS\USER2\TEST.EXEC (RFS'This example loads the exec TEST.EXEC from RFS into virtual storage. Subsequent calls of TEXT.EXEC will use the loaded copy.
Note:
- If an exec is loaded into virtual storage, it is automatically shared by all users.
- If an EXECLOAD is performed to replace an in-storage exec with a newer copy, a shadow of previous copies is kept in virtual storage until all active execs based on these copies end. This is accomplished by a use count.
- Execs that are loaded into virtual storage are always used before other execs. Name your programs carefully because, if two execs have the same name and one resides in your RFS current directory and one is loaded into virtual storage, you cannot run your RFS copy.
- When an exec is loaded into virtual storage, the copy of the exec inherits security characteristics from where it was loaded. For example, any user can run an exec from a CICEXEC data set and any exec loaded from CICEXEC can use REXX/CICS® authorized commands. See Modify the CICS initialization JCL.