Stacking copies on tape

When you dynamically allocate copy data sets, you can use the STACK YES option to have all copy data sets allocated with the same tape OUTPUT descriptor stacked on tape.

The stacking order is determined by the order of the input image copies, if any. If no input stacked copies exist, BMC AMI Recover uses the default stacking order that is used by BMC AMI Copy wildcard processing. If there is a mix, the copies with corresponding stacked input image copies are stacked first, followed by the remaining copies in default order.

Related topics

Dynamic-allocation-output-image-copy-data-sets

INDEP-OUTSPACE

INDEPENDENT-OUTSPACE

When you 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 TMM (Tape Mount Management), 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 Recover program AFRMAIN to the TMM exclusion list.

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 command 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
RECOVER TABLESPACE A.B ..... options
   OUTCOPYDDN(LPCOPY,LBCOPY) ..... more options
RECOVER TABLESPACE C.D ..... options
   OUTCOPYDDN(LPCOPY,LBCOPY) ..... more options
RECOVER TABLESPACE E.F ..... options
   OUTCOPYDDN(LPCOPY,LBCOPY) ..... more options


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*