Stacking image copy data sets

Use the STACK_NAME keyword to specify the name of a stack group to which the image copy data set belongs. The same name is specified for each image copy that is to be included in the group. All image copy data sets that are part of the same stack group are written onto the same tape volume (or volumes) as file number 1, 2, 3, and so on.

The following sample specifies that an image copy data set be created for each area in the database. The output data sets are all to be written to the same tape volume.

Using the STACK_NAME keyword

IMAGECOPY DBD=
dbdname,IAREA=ALL
  IC STACK_NAME=NAME1,UNIT=TAPE,DISP=(NEW,CATLG),
     DSNAME='<dataset-name-mask>'

Dynamic allocation is always used for stacked data sets. When an IC subcommand containing a unique value for the STACK_NAME keyword is encountered, values that are specified for the UNIT, VOLCNT, VOLSER, EXPDT and RETPD keywords (if any) on the IC subcommand are saved; these values will apply to all image copy data sets that are written to the stack. The UNIT keyword must be specified and must refer to a tape device type. All other dynamic allocation keywords, such as DSNAME, pertain to the individual output image copy data set that is being defined. DISP=NEW is required for stacked data sets; there are no restrictions on the remaining parameters for the DISP keyword.

In the following sample, two image copy data sets are requested for each area in the database. You cannot request that both copies be written to the same stack. You can, however, specify a different STACK_NAME keyword on each IC subcommand. You can also mix stacked and non-stacked image copy processing within the same primary command.

Unacceptable use of the same stack name within a single command

IMAGECOPY DBD=<dbdname>,IAREA=ALL, ...
  IC   STACK_NAME=NAME1, ...
  IC   STACK_NAME=NAME1, ...




This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments