Jobs That Write Directly to CDAM Datasets

CDAM Parameter Requirements

  IN      JOB6-CDAM-CREATED    ODAT                                          

  WHEN IN QUEUE N       TIME FROM      UNTIL       INTERVAL     PRIORITY      

  DSN     LAST=YES                                                            

If you use the CDAM Direct Write facility, your report decollating missions will decollate directly from the CDAM datasets. We therefore must tell the report decollating mission which compressed dataset you want to decollate.

You specify retrieval information in the DSN field so that Control-D can identify which CDAM dataset you want to decollate. You do not specify the JES dataset name in this field. You use the special CDAM retrieval parameters. It is unnecessary to specify the JOBNAME retrieval parameter because, by default, Control-D will look for CDAMs that match the job name of your specific report decollating mission.

BMC recommends that you use the retrieval statement LAST=YES when decollating from CDAM datasets. This means that you will decollate only the last CDAM datasets created by the job. If you do not use this parameter, you will be decollating all CDAM datasets that exist for the job, including those from previous runs, which for some implementations may be very useful.

You should also note that if you do not specify any other Runtime parameters, the report decollating mission will run as soon as it is placed in the Active Missions file. To avoid this, you should either define the report decollating mission so that it waits for a condition before it can execute (using the IN parameter), or schedule the report decollating mission after the CDAM dataset has been created.