The resource definitions you must add to the CSD file for each managed CICS® system are distributed in CSD upgrade load modules in CICSTS31.CPSM.SEYULOAD.
The names of the load modules, the environment for which they are used, and the name of the resource group (created using the definitions the load modules contain) are:
Load module | EYU9nnG1, where nn represents the CICS level (for example, 63 refers to the CICS element in CICS TS for z/OS® Version 2.3, and 64 refers to the CICS element in CICS TS for z/OS Version 3.1). |
Environment | MAS - USELAPCOPY(NO) |
Resource group | EYU310G1 |
Sample JCL that you can use to include the definitions is supplied in the member EYUJCLGN in the CICSTS31.CPSM.SEYUSAMP library. You can edit this JCL, as shown in Figure 54, to:
//CSDUP EXEC PGM=DFHCSDUP
//STEPLIB DD DSN=cics.index.SDFHLOAD,DISP=SHR
// DD DSN=cpsm.index.SEYULOAD,DISP=SHR
//DFHCSD DD DSN=cics.dfhcsd,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
UPGRADE USING(group_load_module)
ADD GROUP(EYU310G1) LIST(list_name)
/*
Modify the sample JCL to provide the following information:
To avoid your transaction names clashing with those used by CICSPlex SM, you should review the names of the transactions defined in the appropriate EYU310Gn group in the CSD. The CICSPlex SM MAS transaction names are all of the form COxx.
A return code of 4 is expected from this run of DFHCSDUP. This is because, before adding the designated group to the CSD, the job attempts to delete any group with the same name.
To run the MAS using an USELPACOPY(YES) group, the appropriate load modules must be moved to the SYS1.CICSTS31.CPSM.SEYULPA data set. For additional information, see Using CICSPlex SM modules in the MVS link pack area.