CAIENF Utilities › CAS9DCMR - DCM Mapper

CAS9DCMR - DCM Mapper

This is a stand-alone utility program that is invoked through standard z/OS JCL, as follows:

Note: Sample JCL is located in .CAW0JCL(CAS9DCMR).

//jobname  JOB  job card information
//STEP1   EXEC  PGM=CAS9DCMR,REGION=0M,
//                     PARM='DCM(dcm1,dcm2,…,dcmn)'
//*
//STEPLIB DD DSN=common-services-CAW0LOAD,DISP=SHR
//SYSPRINT  DD  SYSOUT=*
//SYSPUNCH DD  DSN=&&DROPSQL,
//                       DISP=(NEW,PASS),
//                       UNIT=SYSDA,
//                       SPACE=(TRK,(5,1)),
//                       DCB=(LRECL=80,BLKSIZE=800,RECFM=FB)
//DCMLIB     DD  DSN=dcm-library-dataset-name,DISP=SHR
//SYSIN       DD  *
utility control statements
//

The only utility control statement allowed is the DCM statement which identifies which DCMLIB members are to be mapped:

DCM(dcm1,dcm2,…,dcmn)

There can be more than one DCM control statement.

Any statement that contains an asterisk (*) in column 1 is treated as a comment. It is printed on the input statement report, but the information in the card is ignored.

The DCM control statements can be provided from the following different sources:

1. If only one control statement is needed, the SYSIN DD statement can be omitted, and the required DCM control statement can be passed from the PARM field on the EXEC card.
2. Multiple control statements can be provided by the SYSIN DD statement.
3. Control statements can be passed in the PARM field and from the SYSIN DD statement. In this case, the statement passed in the PARM field is processed first, and then all the ones contained in the SYSIN data stream.

The output from the program is divided into four parts:

1. A listing of all the control statements processed and any error messages associated with them or the DCM members referenced
2. A map of the Event Tables defined in the DCM.
3. A map of all the fields contained in each of the Event Tables.
4. A series of comments and DROP TABLE SQL commands that can be passed to the DBSQLPR utility provided with CA Datacom/AD. These statements are written to the SYSPUNCH DD statement if it is present. If the SYSPUNCH statement is omitted from the run, no error message is produced nor are the DROP TABLE statements generated.

   Note: DROP TABLE SQL commands should only be used to REPLACE a DCM, as advised in the Best Practices Guide.

   Note: If the CAIENF DCM (CAS9DCM0) is chosen to report on, no DROP TABLE SQL statements will be output for this particular DCM. This is because some of the CAS9DCM0 event tables are required for CAIENF to function properly. If CAS9DCM0 ever needs to be replaced, the replacing code from either a PTF or a new CCS release, will provide specific instructions and sample JCL to perform the replacement.