CA Dynam for VSE User Guide

Managing Special Files
Releasing Work Data Sets
Work data sets have two characteristics which differentiate them from other
data sets. They are as follows:
• You can release work data sets and return them to the scratch pool
immediately at CLOSE by specifying the RELEASE option (R or 04) on the
TLBL statement.
• Unreleased work data sets are retained for as long as specified in the
CA Dynam/T option record. While in use, work data sets are completely
protected. You can release them at any CLOSE (input or output).
Defining Independent Files
Both partition-independent and CPU-independent files are supported by all
CA Dynam/T batch programs.
Partition-Independent Files
CA Dynam/T's support for partition-independent files allows work data sets to
be used in any partition without JCL modification. If the two characters '=='
are found in the file ID when a TLBL is processed at program OPEN,
CA Dynam/T replaces them with the SYSLOG ID (partition identifier) of the
partition in which the job is running.
For example, if the following TLBL were processed in the BG partition,
CA Dynam/T would replace the file ID '==WORK' with BGWORK.
// TLBL SYS010,'==WORK'
If the same TLBL were processed in the F3 partition, the resulting file ID would
be F3WORK.
Establish one (or more) work data set names for each partition with DYNCAT;
CA Dynam/T makes sure that the same name is never used in more than one
partition simultaneously.
Example:
DEFINE 'BGWORK' WORK=YES
DEFINE 'F1WORK' WORK=YES
DEFINE 'F2WORK' WORK=YES
For users running other software which changes the SYSLOG ID, the special ID
characters (==) are replaced with the appropriate SYSLOG ID found in the
PUB2.
Chapter 2: Maintaining Tape Files 2–49