Output copy data set options
You can set a wide range of output copy data set parameters that apply to all of the supported backup utilities.
The options are defined separately for each type of output copy (local site primary, local site backup, recovery site primary, recovery site backup) and are available at the subsystem and object set levels. The options are listed alphabetically in the following table, Output data set option defaults and validity, along with the defaults that, in this instance, are all BMC AMI Recovery Manager defaults.
You can specify separate output data set options when BMC AMI Copy is the backup utility, as follows:
- FULLDDN—use FULLDD output data sets when a BMC AMI Copy FULL AUTO incremental copy is escalated to a full image copy. BMC AMI Recovery Manager generates FULLDDN syntax when you have set the Support Full Copy DDs (FULLDDN) BMC AMI Copy option to Yes.
- BIGDDN—use the BIGDD output data set options when you want full copies that exceed a specified number of pages to be allocated to a different output descriptor or data set name. BMC AMI Recovery Manager generates BIGDDN syntax when you have set the appropriate BMC AMI Copy options. The Support Outsize Option (BIGDDN) option must be set to Yes and the Outsize Threshold for BIGDDN must be set to a value other than 0.
For more information on BMC AMI Copy backup options, see BMC-AMI-Copy-backup-options.
Option | Default | Description |
|---|---|---|
ACPGDG Keyword: none | Null | Specifies a fully qualified data set name to define a GDG base for this copy The named data set must contain the control cards that are needed to perform an IDCAMS DEFINE as well as the symbolic variable &BASE, which replaces the GDG base name. The variable 'xx' is LP, LB, RP, or RB, as appropriate. |
DSSNAP Keyword: DSSNAP | NO | Specifies making a hardware-based Instant Snapshot copy of Db2 data, as follows: Yes—make a hardware-based Instant Snapshot copy Auto—made a hardware copy if possible, but fall back to a standard copy if the hardware copy fails (for example if XBM, SUF, or the required hardware is not in place) No—make a standard copy |
Allocation type Keyword: SPACE | Cylinder | Specifies whether the primary and secondary allocations quantities are expressed in cylinders or tracks for disk units
|
Catalog Keyword: CATALOG | Yes | Catalogs the data sets in the operating system catalog |
Data set name Keyword: COPYDSN | &USERID.&DB.&TS.&TYPE&DATE.T&TIME | Specifies the name of the disk or tape data set for the current copy type The BMC AMI Recovery Manager default is &USERID.&DB.&TS.&TYPE&DATE.T&TIME. |
EATTR for EAV Keyword: EATTR | Not specified | Specifies whether a data set supports extended attributes or not. Specifying no value for EATTR allows the value for EATTR to be set by an SMS DATACLAS. Valid values are:
|
Encrypt the copy Keyword: ENCIPHER | NO | Specifies making encrypted image copies to prevent unauthorized access to sensitive company information. (This option is only displayed when you are using BMC AMI Recovery Manager as part of the Recovery Management for Db2 solution and are using the solution password.) Copy encryption is incompatible with DSSNAP YES or AUTO. Copy encryption is incompatible with compressed indexes. DSSNAP is set in the BMC AMI Copy Specific Options panel. |
Expiration date Keyword: EXPDT | 1999/000 | Specifies the expiration date for a tape copy data set, in the format yyyy/ddd The BMC AMI Recovery Manager default is 1999/000, which indicates no expiration. Expiration date and Retention period are mutually exclusive. |
Migrate copy data sets Keyword: MIGRATE | NO | Specifies Hierarchical Storage Management (HSM) migration of copy data sets when BMC AMI Copy is finished with them This option is valid only when copying to disk and is available only with BMC AMI Copy version 6.4 or later. Valid values are as follows:
|
Model data set name (DCB) Keyword: MODELDCB | Null | Specifies the name of a cataloged data set used to define the model DCB The data set name must be fully qualified. |
Retention period Keyword: RETPD | None | Specifies the tape copy data set retention period in days (1 through 999) |
SMS data class Keyword: DATACLAS | Null | Specifies a valid SMS data class name for disk data sets The name must not exceed 8 characters. BMC AMI Recovery Manager forces Catalog Yes when you specify this option. |
SMS management class Keyword: MGMTCLAS | Null | Specifies a valid SMS management class name for disk data sets The name must not exceed 8 characters. BMC AMI Recovery Manager forces Catalog Yes when you specify this option. |
SMS storage class Keyword: STORCLAS | Null | Specifies a valid SMS storage class name for disk data sets The name must not exceed 8 characters. BMC AMI Recovery Manager forces Catalog Yes when you specify this option. |
Stack (copies on tape) Keyword: STACK | NO | Specifies whether to stack image copies of the same type contiguously on the same tape Always respond No to Stack if you specified a disk unit for the image copy data sets; otherwise you will receive an INVALID COMBINATION message. You will also receive that message if you respond Yes to Stack and leave Tape blank. For Recovery Management for Db2 solution only - you can specify Cabinet to create cabinet copies. Cabinet copies can be made to either disk or tape. Stack is not valid with compressed indexes. For more information, see the Recovery Management for Db2 documentation. |
Tape Keyword: TAPE | NO | Specifies whether the unit is a tape or disk, as follows: Yes—tape (you must also provide the name of a tape unit at the Unit prompt). No—disk |
Unit Keyword: UNIT | SYSALLDA | Specifies the name of the disk or tape unit to which the image copy data sets are written |
Volume count Keyword: VOLCNT | 0 | Specifies the largest number of tape volumes (1 through 255) that you expect to create This option applies only to tape data sets. You can leave this field blank if you expect no more than five tape volumes to be created. |
This section contains the following topic:
Related topics