Step 1B. Define Lsys Identifying Tokens (Re-Linkedit IMS Modules) (Option 1.6)
Whenever an IMS based batch JOB is executed, the Logical System it is to be executed in must be identified. This identification is achieved in one of three ways:
- Put Lsys identifying token in the second positional JOB card parameter.
- Put an Lsys identifying token in place of the IMSID in the PARM field of the DFSRRC00 program.
- Add a COPEBSYS DD statement where the Lsys Identifying token is a temporary dataset name. For example:
//COPEBSYS DD UNIT=SYSDA,SPACE=(TRK,1),DSN=&&Lsys-token
The tokens that identify a Logical System are defined with Option 1.6. This ISPF-based application puts the Lsys identifying tokens into a load module named COPEPSYS and linkedits it into the IMS RESLIB. It also transfers some COPE modules into the IMS RESLIB and re-Linkedits DFSRRC00 and other utility modules into various datasets.
Before the application is executed, the COPETOOL PROCS member must be reviewed to specify what utility modules are present in an installation. The member may be accessed by specifying EVARS;EDIT COPETOOL on the COPE primary ISPF menu. An example of the result is shown in the following figure.
COPETOOL Content
The load module datasets present for various utilities in an installation are identified and an alternate dataset is specified for each. The COPE Option 1.6 application generates Linkedit statements that relink edit the utility load modules and puts them in the alternate datasets. The alternate datasets are specified in the JCL whenever the utility is executed in a COPE environment.
Selecting COPE ISPF Option 1.6 and then specifying G in the command field results in the following figure.
Specify COPE Systems
If a IMS RESLIB is shared between multiple COPE systems, the ZDEFAULT dataset and member name of all the systems must be specified. The dataset name and member name can be found on the primary COPE ISPF panel.
Entering the END key (PF3) results in the following figure.
Lsys Identifying Token Specification.
Different tokens may be specified for the JOB Card and the PARM field IMSID. Generally identical tokens are specified. The IMSID token may be 8 characters even though the field is limited to 4 characters in normal usage.
When definition is completed, enter END (PF3). Check the resulting generated job, submitted after the SYSLMOD statements of the generated job, to ensure the target datasets are correct.