|
|
|
|
|
CDAM files are the main storage mechanism for all reports handled by Control-D.
Control-D automatically creates compressed versions of reports into CDAM files as Control-D decollates the output from the spool (you can of course use the CDAM direct-write option to bypass the spool altogether). These compressed datasets allow for a reduction of between 30% to 70% of the space allocated for the report.
Normally, a CDAM file is created for every JES dataset that Control-D handles. This can be overridden using the CDAM allocation options that we will discuss in Phase 7. At this stage, let us assume that one CDAM dataset is created per JES dataset.
We recommend that CDAM files be kept on DASD for a minimal amount of time. This is normally determined by the length of time that the report output needs to be viewed online by the users. Control-D archives CDAM datasets to tape using backup missions. However, the backup missions only copy the CDAM files to tape, they do not delete them from disk. This method provides the great advantage of having a backup of reports while they are still on DASD for online viewing purposes (in case of a DASD crash).
A special utility called CTDDELRP is available to delete CDAM datasets from disk.
Parent Topic |