CA Dynam for VSE User Guide

Processing Unchained Multifile Tapes
A multifile-volume is to be read and a new version created in one job stream.
Options direct CA Dynam/T to the correct tape drives for the second and third
files.
Example:
Multiple TLBLs with identical DTFNAMES
Submit identical dtfnames consecutively if you are including them in one job
step. This restriction is imposed by IBM label record management routines.
// TLBL UIN,'FILE1,H,D'
// TLBL UIN,'FILE2,H,D'
// TLBL UIN,'FILE3,W'
// TLBL UOUT,'OUTPUT FILE1,H,D'
// TLBL UOUT,'OUTPUT FILE2,H,D'
// TLBL UOUT,'OUTPUT FILE3,H'
NOT
// TLBL UIN,'FILE1,H,D'
// TLBL UOUT,'OUTPUT FILE1,H,D'
// TLBL UIN,'FILE2,H,D'
// TLBL UOUT,'OUTPUT FILE2,H,D'
// TLBL UIN,'FILE3,W'
// TLBL UOUT,'OUTPUT FILE3,W'
Processing Unchained Multifile Tapes
The STACK= TLBL option can be used to specify that a file is to be part of a
multifile set. To use this feature you have to code a STACK= parameter on
each TLBL of a multifile set.
Valid STACK parameters are A to Z, 1 to 9, and ‘*’. By default, A to Z cause
the tape to rewind at close and 1 to 9, or ‘*’, cause the tape not to rewind at
close. Aside from this, there is no difference between one STACK= parameter
and another. They simply allow a way to differentiate one unchained multifile
tape from another within the same jobstream.
By using the HOLD(H) TLBL option with no close tape disposition, R, U, and so
on, the rewind default for the A to Z parameters can be overridden so that the
tape does not rewind at close. You cannot have chained DSNs and unchained
DSNs on the same tape.
To stack other files on a tape you must always reference the last active file on
that tape.
Chapter 2: Maintaining Tape Files 2–67