Stacking copies on tape

When you use multiple COPY statements in your SYSIN data set and dynamically allocate copy data sets, you can optionally stack output copies of the same type (LP, LB, RP, or RB) contiguously on the same set of tapes.

Warning

If you are using Tape Mount Management (TMM), be aware that TMM intercepts any data set allocation whether dynamic or otherwise. If you want the copies on tape and use STACK YES with TMM, add the BMC AMI Copy program ACPMAIN to the TMM exclusion list. If BMC AMI Copy detects that the allocation has gone to disk instead of tape, it discontinues stacking and issues message BMC47357.

When you want to stack copies of more than one type on tape (such as local site primary and local site backup), you must use a different OUTPUT descriptor for each type and stack the copy types on different tape units. For example, the following statements stack local site primary copies of table spaces A.B, C.D, and E.F contiguously on tape unit CARTLP and the corresponding local site backup copies contiguously on tape unit CARTLB:

OUTPUT LPCOPY UNIT CARTLP ...options ... STACK YES
...more options
OUTPUT LBCOPY UNIT CARTLB ...options ... STACK YES
...more options
COPY TABLESPACE A.B
.....options
     COPYDDN(LPCOPY,LBCOPY) .....more options
COPY TABLESPACE C.D .....options
     COPYDDN(LPCOPY,LBCOPY) .....more options
COPY TABLESPACE E.F .....options
     COPYDDN(LPCOPY,LBCOPY) .....more options

Important

If you specify STACK=YES and a value for REALDD (see Using-REALDD), REALDD will always be used.

Stacking copies on tape

On this page