OUTCOPYDDN specification
OUTCOPYDDN overrides the default ddnames or ddname prefixes that are used by BMC AMI Recover.
The syntax diagram for the OUTCOPYDDN specification is in RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE syntax.
OUTCOPYDDN (DDName1,DDName2)
You can use OUTCOPYDDN (DDName1,DDName2) to override the default ddnames or ddname prefixes that are used by BMC AMI Recover for a table space or index to specify copy data set ddnames in the JCL. OUTCOPYDDN can also reference an output descriptor named with an OUTPUT command statement if the copy data set is to be dynamically allocated.
Important
The following restrictions apply only if OUTCOPYDDN refers to a DD statement in the JCL:
When a table space or index has fewer than 100 partitions, you can specify any value of up to six characters. If copies are being made by partition, this value is a prefix. If DSNUM ALL and OPTIONS OUTCOPY ASCODED are specified, this value is a ddname.
For a table space or index with 100 or more partitions, the default values for all partitions are BMCCY and BMCCZ, and you can specify any value of no more than five characters.
For a nonpartitioned table space or index, if DSNUM ALL is specified or the highest value of DSNUM in the run is less than 100, you can specify any value up to six characters. If the highest value of DSNUM is 100 or higher, you can specify any value of up to five characters.
The ddnames specified with OUTCOPYDDN are optionally enclosed in parentheses but must be separated by a comma. For more information, see Copy data set ddname construction for JCL-allocated data sets.
OUTCOPYDSN (dataSetName1, dataSetName2)
You can use OUTCOPYDSN (dataSetName1, dataSetName2) to override the data set name specified by an output descriptor for OUTCOPYDDN for a dynamically allocated output image copy. Use of OUTCOPYDSN when the output image copy is not dynamically allocated is an error.
Comments
Log in or register to comment.