CDAM writes the compressed sysout to a sequential dataset. Each sysout may span one or more datasets. The datasets are allocated on the unit specified in the CDAM parameters, without secondary allocation parameters. The workflow of CDAM is as follows:
If allocation fails (that is, a space in the specified size cannot be found), the CDAM attempts half of the previous size and continues to do so until the allocation succeeds. Therefore, CDAM abends on SB37 only when the last single free track in the specified unit is full, that is, there is no remaining space in the entire unit.
In this way, CDAM makes use of otherwise unusable areas on the disks. The disk normally contains unused tracks which cannot be used by the standard dataset allocation algorithm. These areas can be used by CDAM. For example, a CDAM dataset could be allocated as follows:
Note: This example is exaggerated to illustrate the CDAM allocation algorithm.
Table 278 CDAM Dataset Allocation – Example
Logical Extent |
No. of Tracks |
---|---|
1st logical extent |
50 tracks |
2nd logical extent |
100 tracks |
3rd logical extent |
50 tracks |
4th logical extent |
25 tracks |
5th logical extent |
6 tracks |
6th logical extent |
1 track |
7th logical extent |
1 track |
8th logical extent |
1 track |
9th logical extent |
1 track |
When a compressed sysout is read by CDAM, the record format, block size and the record length of the dataset are retrieved. The report takes the original LRECL, BLKSIZE and RECFM specifications (from the ACB/DCB) as it had when produced by the application program.
Parent Topic |