|
|
|
|
|
Control-M/Tape does not record tape activity that is performed on temporary files. If a temporary file is created on a scratch tape, the tape remains a scratch tape throughout the life cycle of that temporary file.
Control-M/Tape considers a file to be temporary only when it did not previously exist (that is, it is newly created), the volume that the data set is to be read from or written to is scratch, and one of the following applies:
Note: If CA1 was specified for Control-M/Tape installation parameter EXPDTYPE, and the expression LABEL=EXPDT was specified for the file, the file is not considered temporary, even if one of the preceding conditions is true.
Note: A volume that is used as temporary storage might remain Active in the ATL, if no special measures are taken. This is because such volumes are marked as SCRATCH and are no longer managed by the Retention Management process, which passes SCRATCH requests to ATL.
To resolve this issue, set the CTTPARM parameter TMPVLACT to Y. This instructs Control-M/Tape to set the volume to ACTIVE, PENDING_SCRATCH after the job that uses the volume completes. As a result, the volume will become SCRATCH during the next Retention Management run in both the Control-M/Tape database and the ATL.
If you set TMPVLACT=N, Control-M/Tape ignores any volume used for temporary files. The volume remains as SCRATCH in Control-M/Tape after the job that uses the volume completes, but remains ACTIVE in the ATL.
Parent Topic |