|
|
|
|
|
A multi-job CDAM dataset differs from a regular CDAM dataset in that it contains sysouts of many jobs instead of only one job.
The allocation algorithm of a multi-job CDAM dataset allocates a large specified space for the dataset. All the job’s sysouts are written to the dataset. As soon as a job is decollated, its sysouts are available for online viewing.
However, unlike regular CDAM allocation options, the file remains allocated to the Control-D monitor. The monitor adds additional SYSOUTs of jobs to the same file. When the first logical extent of the CDAM file is full, CDAM allocates a second logical extent. CDAM continues writing to the logical extent until the end of the processed job.
Next, the file (which now contains sysouts of many jobs) is deallocated, and the remaining space in the second extent is freed. When a new job is processed, a new multi-job CDAM dataset is allocated with the specified space (as first logical extent) and the process resumes.
This type of CDAM dataset combines the benefits of one large pre-allocated reports database designated to contain many reports, with the benefits of dynamic allocation of needed space when the reports database is full.
Multi-job CDAM files, created by using CDAM parameter ALLOCOPT=JOBSDSN1 or ALLOCOPT=JOBSDSN2, cannot be used as input for a report decollating mission.
Parent Topic |