Updating the CSD files using DFHCSDUP (CMAS)

Start of changeThe resource definitions you must add to the CSD file for each CICS® CMAS are distributed in the EYU964G0 modules of the CICSTS31.CPSM.SEYULOAD library, where nn represents the CICS level. End of change

Sample JCL that you can use to include the definitions is in the member EYUJCLG0 in the CICSTS31.CPSM.SEYUSAMP library. You can edit this JCL, as in Figure 52, to:

  1. Define the CMAS group of resource definitions to the appropriate CSD file.
  2. Add the CMAS group list to the CSD.
Figure 52. Sample JCL to run DFHCSDUP
//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)
/*

Modify the sample JCL to provide the following information:

STEPLIB
Identify:
DFHCSD
Identify cics.dfhcsd as the CICS CSD file to be updated.
SYSIN
You must identify the load module (EYU9nnG0) that contains the resource definitions group that is required to run the CMAS (EYU310G0).

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.

Note:
You should not normally run user transactions in a CMAS. However, if you do choose to define your own transactions to the CMAS, you should be aware that transaction IDs used by CICSPlex SM in the CMAS have no specific format. To avoid conflict between your names and those that are used by CICSPlex SM, you should review the transactions that are defined in the CSD group EYU310G0. For a list of these transactions, see the CICS RACF® Security Guide.
[[ Contents Previous Page | Next Page Index ]]