OUTPUT syntax options reserved for disk data sets


This section describes options that apply only to copy data sets written to disk devices.

Syntax diagram of OUTPUT options reserved for disk data sets

OUTPUT_syntax_disk_options.png

Option

Description

DISKEXPD date

When you use dynamic allocation, specify the DISKEXPD date in the descriptor named after the OUTPUT keyword to set a new expiration date for the current disk copy data set. If you do not specify DISKEXPD, no expiration date will be specified.

The value of date must be in the format YYDDD, YYYYDDD, or YYYY/DDD where YYYY is the 4-digit year, YY is the last two digits of the year, and DDD is the 3-digit Julian day (001 through 366).

Important

A date with a two-digit year is passed as is to dynamic allocation. For years beyond 1999, depending on your environment, this might not produce the appropriate result. We recommend using a four-digit year.

This option is not valid when you use REALDD and causes an error.

Important

When it is specified, DISKEXPD takes precedence over DISKRETN.

DISKRETN integer

When you use dynamic allocation, specify DISKRETN integer in the descriptor named after the OUTPUT keyword to set a new retention period (in days) for the current disk copy data set. If you do not specify DISKRETN, no retention period will be specified.

The value of the integer must be in the range 0 through 9999. A value of 0 indicates there is no retention of the disk copy data set.

Important

When DISKEXPD is specified, it takes precedence over DISKRETN.

DSSNAP

Use the DSSNAP option to have BMC AMI Copy make Instant Snapshot copies in conjunction with the BMC SNAPSHOT UPGRADE FEATURE (SUF) or EXTENDED BUFFER MANAGER (XBM) product. Valid values are DSSNAP NO, DSSNAP YES, and DSSNAP AUTO. The default value is DSSNAP NO.

Instant Snapshots are hardware-based, non-standard copies, which do not require the I/O needed to make a standard copy. They are registered in the BMCXCOPY table. These copies are recognized and restored by other BMC products that access the BMCXCOPY table. For more information and for rules and requirements related to Instant Snapshots, see Making-Instant-Snapshot-copies.

Important

If you intend to make Instant Snapshots of spaces that have a 32 KB page size using SHRLEVEL CHANGE, we recommend that you set DSVCI=YES in DSNZPARMS so that Db2 data sets are allocated with a control interval size that matches the Db2 page size.

Values of DSSNAP

Value

Description

DSSNAP NO

(Default) DSSNAP NO specifies that BMC AMI Copy is to make a standard copy—not an Instant Snapshot.

DSSNAP YES

DSSNAP YES indicates that BMC AMI Copy should make only an Instant Snapshot copy.

DSSNAP YES and STACK CABINET (which specifies cabinet copies) are mutually exclusive options, and you cannot use them on the same OUTPUT command.

DSSNAP AUTO

DSSNAP AUTO makes Instant Snapshots if possible, but falls back to a standard copy if necessary (for example, XBM or the required hardware is not in place).

Important

DSSNAP AUTO is not supported for certain catalog and directory spaces.

EATTR

Use EATTR to specify whether a data set supports extended attributes or not. If you do not specify EATTR on the OUTPUT command, BMC AMI Copy uses the value of the EATTR installation option (EATTR=). The EATTR installation option defaults to EATTR=, which is the equivalent of EATTR=NONE.

Valid values for EATTR are NONE, OPT, and NO.

Values of EATTR

Value

Description

EATTR NONE

Using NONE allows you to have your environment set up to use extended attributes.

EATTR NONE specifies no value for EATTR and allows the value for EATTR to be set by an SMS DATACLAS

Using NONE allows you to have your environment set up to use extended attributes.

EATTR OPT

EATTR OPT specifies that extended attributes are optional for the data set.

You must set EATTR=OPT to allocate an extended format sequential data set. Using EATTR=OPT, BMC AMI Copy supports sequential data sets in the cylinder-managed portion of EAVs.

Extended format sequential data sets must be allocated on SMS-managed volumes and the size of the data set must be greater than the EAV break point, which is typically 10 cylinders.

EATTR NO

EATTR NO specifies that the data set cannot have extended attributes.

LBVOLS (vol1, vol2, ...)

Specify LBVOLS to provide a new list of disk volumes for storing local site backup copies for the named descriptor. The number of entries in the list must not exceed the value specified by VOLCNT in the named descriptor (see VOLCNT). If the data set is uncataloged, BMC AMI Copy truncates the list recorded in SYSIBM.SYSCOPY to reflect the actual volumes used.

If you do not specify LBVOLS for the named descriptor, BMC AMI Copy uses the installation option value (if any). If you do not want to use a value for LBVOLS and there is an installation option default, specify LBVOLS(NONE).

Warning

There must be enough space on the first specified volume to allocate the primary space required for the output data set.

MAXPRIM integer

Specifying MAXPRIM for the named descriptor allows you to do the following things:

  • Set a new value for the maximum amount of disk space (in the units specified by SPACE) that can be allocated as primary space
  • Put an upper limit on the value calculated by PCTPRIM (in the case of large table spaces)

A nonzero value for an integer establishes an upper limit for primary space allocation, while a value of zero specifies no limit.

If you do not specify MAXPRIM in the named descriptor, BMC AMI Copy uses the installation option value. The default for the installation option is 559.

MIGRATE

Use the MIGRATE option to specify Hierarchical Storage Management (HSM) migration of copy data sets when BMC AMI Copy is finished with them. Valid values are MIGRATE NO, MIGRATE HSM, and MIGRATE HSM ML2, with a default of MIGRATE NO.

The following restrictions apply when you use the MIGRATE option:

  • You cannot specify the REALDD option.
  • You must specify a disk device for the UNIT option on the OUTPUT command.
  • You cannot migrate Instant Snapshot copies.

If BMC AMI Copy successfully issues the migration call, the job ends without an error. However, the migration process itself is asynchronous and might not complete until after the BMC AMI Copy job is finished. If the migration process fails to complete successfully, the BMC AMI Copy job might still end with condition code zero.

If the migration command reports an error to BMC AMI Copy, the job issues the following warning:

BMC47419W MIGRATION COMMAND FAILURE - RC =returnCode,
REASON =reasonCode

Values of MIGRATE

Value

Description

MIGRATE NO

(Default) BMC AMI Copy works as it has in the past when you specify MIGRATE NO. No migration call is made to HSM.

MIGRATE HSM

MIGRATE HSM specifies migration to compressed disk.

Important

Ensure that you have enough space available if you specify MIGRATE HSM.

MIGRATE HSM ML2

MIGRATE HSM ML2 causes immediate migration to a migration level 2 (MIGRATIONLEVEL2) volume.

NBRSECD integer

Specify NBRSECD for the named descriptor when you want to set a new value for the size of secondary allocations. After the primary allocation is calculated, the remaining space is secondary space and can be divided into 1 to 15 parts. This is specified by an integer, which must be in the range 1 through 15.

If you do not specify NBRSECD in the OUTPUT statement, the value in the current default descriptor is used. The default for the installation option is 10.

Important

The size of the secondary allocation cannot be less than 10% of the primary.

PCTPRIM integer

Specify PCTPRIM for the named descriptor to set a new value for the percentage of the total space that needs to be allocated as primary space. If you do not specify PCTPRIM for the named descriptor, BMC AMI Copy uses the installation option value. The default for this installation option is 100.

Important

For large table spaces, the primary allocation calculated by PCTPRIM might be too large. To override the calculated value, you can use MAXPRIM.

RBVOLS (vol1, vol2, ...)

Specify RBVOLS to provide a new list of disk volumes for storing recovery site backup copies for the named descriptor. The number of entries in the list must not exceed the value specified by VOLCNT in the named descriptor (see VOLCNT). If the data set is uncataloged, BMC AMI Copy truncates the list recorded in SYSIBM.SYSCOPY to reflect the actual volumes used.

If you do not specify RBVOLS for the named descriptor, BMC AMI Copy uses the installation option value (if any). If you do not want to use a value for RBVOLS and there is an installation option default, specify RBVOLS(NONE).

Warning

There must be enough space on the first specified volume to allocate the primary space required for the output data set.

RPVOLS (vol1, vol2, ...)

Specify RPVOLS to provide a new list of disk volumes for storing recovery site primary copies for the named descriptor. The number of entries in the list must not exceed the value specified by VOLCNT in the named descriptor (see VOLCNT). If the data set is uncataloged, BMC AMI Copy truncates the list recorded in SYSIBM.SYSCOPY to reflect the actual volumes used.

If you do not specify RPVOLS for the named descriptor, BMC AMI Copy uses the installation option value (if any). If you do not want to use a value for RPVOLS and there is an installation option default, specify RPVOLS(NONE).

Warning

There must be enough space on the first specified volume to allocate the primary space required for the output data set.

SPACE (primary, secondary) allocation unit

Specify SPACE to set the output allocation units (tracks or cylinders) for the named descriptor. Specify SPACE TRK to allocate the output in tracks. Specify SPACE CYL to allocate the output in cylinders. If you do not specify this option for the named descriptor, BMC AMI Copy uses the installation option value. The default value for the installation option is CYL.

If you do not want primary and secondary space requirements (primary, secondary) to be automatically calculated, specify the values you want in parentheses, as in the following example: SPACE (200,100) CYL.

STACK CABINET

Specify STACK CABINET to request cabinet copies to disk or to tape. For more information about cabinet copies, see Making-cabinet-copies.

STACK CABINET and DSSNAP YES (which specifies Instant Snapshots) are mutually exclusive options, and you cannot use them on the same OUTPUT command.

Important

Making cabinet copies is a feature of the BMC Recovery Management for Db2 solution and requires a valid Recovery Management for Db2 solution password.

For cabinet copies, because there is only one data set name for the entire cabinet file, use generic values for DSNAME (DSNAME). Avoid the use of the &DB or &TS substitution variables, although &DB might be appropriate if all copies are for the same database name. If you are multitasking with cabinet copies, you must include &SEQ or &TASK to make the data set name unique across tasks.

VOLUMES (vol1, vol2, ...)

Specify VOLUMES to provide a new list of default volumes for the named descriptor. The new list is used as the default list for LPVOLS, LBVOLS, RPVOLS, and RBVOLS for the named descriptor. The number of entries in the list must not exceed the value specified by VOLCNT for the named descriptor (see VOLCNT). If the data set is uncataloged, BMC AMI Copy truncates the list recorded in SYSIBM.SYSCOPY to reflect the actual volumes used.

If you do not specify VOLUMES for the named descriptor, BMC AMI Copy uses the installation option value (if any). If you do not want to use a value for VOLUMES and there is an installation option default, specify VOLUMES(NONE).

Warning

There must be enough space on the first specified volume to allocate the primary space required for the output data set. This is true for standard copies or Instant Snapshot copies.

 

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