Special Use of Parameter DSN=ODATE.D Option

The DSN parameter can be used by CDAM to force the date when writing directly to a CDAM file. As a default, the date of a CDAM file is taken from the computer clock (that is, the date of its creation). When the DSN parameter is in the following format, the CDAM dataset date is taken from the DSN field:

//XXX DD SUBSYS=(CDAM,'....'),DSN=ODATE.Dyyddd

where

• yy is the year
• ddd is the Julian date

It may be desirable to force a date in the following situations:

• The date can be used as a decollation criteria. When decollating from CDAM datasets using the ON DSN option, it is possible to specify the date as a parameter. The resulting decollation includes all sysouts of the job for that date (including multiple executions on the same day, abends and reruns).
• When different business dates run on the same system date, the decollation criteria may confuse sysouts of different business dates. To prevent this situation, the business date of the job may be forced as the CDAM dataset date.

The date force option is primarily designed for Control-M users who can automatically change the CDAM DSN for each business date using the AutoEdit facility. The special DSN=ODATE option is used to accommodate JCL syntax limitations. It is impossible to pass a symbolic procedure parameter to subparameters of a SUBSYS which are between quotes (all CDAM parameters are supplied between quotes).

Example of the use of parameter DSN=ODATE.D in a Control-M environment:

Sample procedure:

//DEMO   PROC DATE=NONE

//STEP01 EXEC PGM=TEST

//DDNAME DD   SUBSYS=(CDAM,'PREFIX=CTDSYS'),DSN=ODATE.D&DATE

The job (under Control-M):

//JOBNAME JOB .....

//     EXEC DEMO,DATE=%%OYEAR.%%OJULDAY

Users of other scheduling systems can change the date of a CDAM file to the business date using facilities provided by those products.

The report decollating mission parameters for decollating CDAM datasets created in all the executions of the job on the same business date should be:

ON DSN    PREFIX=CTDSYS,DATE=999

999 is automatically replaced with the original Julian scheduling date of the report decollating mission.

The report decollating mission parameters for decollating CDAM datasets which are created in the last execution of the job on the same business date should be:

ON DSN    PREFIX=CTDSYS,DATE=999,LAST=YES

If for some reason, a CDAM dataset is not created for that job on that business date, reports are not selected. If only LAST=YES is used, reports from the previous business date are selected.