Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Copy for Db2 13.1.

OUTPUT syntax options reserved for tape data sets


This section describes the options that apply only to copies written to tape.

Warning

Any SMS DATACLAS, STORCLAS, and MGMTCLAS values existing in the current default output descriptor are used for both disk and tape data set allocations unless overridden in an associated OUTPUT statement. You should check the option settings in the current default output descriptor. In previous releases these settings were ignored for tape allocations.

Syntax diagram of OUTPUT options reserved for tape data sets

OUTPUT_syntax_reserved for tape data sets.png

OUTPUT options reserved for tape data sets 

Option

Description

STACK

The STACK option tells BMC AMI Copy whether to stack the output copies from multiple COPY or COPY IMAGECOPY executions contiguously on the same tape volumes. See Stacking-copies-on-tape and Using-multitasking-with-tape-stacking-or-cabinet-copies for information about using tape stacking.

If you do not specify STACK in an OUTPUT statement, BMC AMI Copy uses the value of the STACK installation option. The BMC AMI Copy installation option default value for this option is STACK=YES.


Values of STACK

Value

Description

STACK NO

Specify STACK NO to override a STACK=YES installation option value. STACK NO tells BMC AMI Copy not to stack output copies contiguously on tape.

STACK YES

Specify STACK YES to override a STACK=NO installation option value. STACK YES tells BMC AMI Copy to stack output copy data sets (of the same type) from multiple COPY or COPY IMAGECOPY statements contiguously on the same tape. When you specify STACK YES, you can optionally use the REALDD option.

Warning

If you are using Tape Mount Management (TMM), 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 Copy program ACPMAIN to the TMM exclusion list. If BMC AMI Copy detects that the allocation has gone to disk instead of tape, it discontinues stacking and issues message BMC47357.

Important

If you specify STACK YES and a value for REALDD, REALDD will always be used.

REALDD DDName

Use the REALDD option to specify that the tape unit be allocated at job initialization by a DD statement DDName in the JCL. This causes the output copy data sets to be stacked on the tape allocated in the JCL.

Important

Most JES3 systems require that all tape allocations be specified in the JCL since the number of tapes to be used must be known at the start of the job. Therefore, REALDD should be coded when working with JES3.

When using REALDD with GROUP YES, MAXTASKS, and a DDFName not greater than 6 characters, the REALDD DDName can act as a prefix instead of a full DDName and is suffixed with the 2-digit task number to create a composite DDName. If the DDName is not found, BMC AMI Copy then looks for the composite name. If the composite name is found, BMC AMI Copy substitutes it for the original REALDD DDNname. This allows you to spread REALDD outputs across multiple tape units.

For example, if you specify REALDD OUT and MAXTASKS (3,3), BMC AMI Copy looks for OUT01, OUT02, and OUT03. Task 1 will use OUT01, task 2 will use OUT02, and task 3 will use OUT03.

When REALDD is used with MAXTASKS (1,1), if BMC AMI Copy does not find an appropriate DD statement, it will then append '01' to the value specified for REALDD and try again. For example, given the following specifications, BMC AMI Copy looks for TAPE in the DD statements. If a DD statement for TAPE is not found, BMC AMI Copy looks for a DD statement for TAPE01.

OUTPUT LOCAL REALDD TAPE UNIT CART
OPTIONS MAXTASKS (1,1)
COPY TABLESPACE A.B COPYDDN(LOCAL)

If you do not specify REALDD for the named descriptor and use STACK YES, you can use the installation option default value for REALDD. Do not associate the same REALDD DDName to more than one output descriptor. Doing so can lead to allocation problems when stacking.

Important

When you use REALDD, dynamic allocation does not occur and the DD statement takes precedence over all output descriptor options except DSNAME, COPYDSN, RECOVERYDSN, and CATLG. In fact, the only parameters allowed when REALDD is specified are UNIT, DSNAME, CATLG, and STACK. All other OUTPUT statement parameters, such as TRTCH, RETPD, and EXPDT, cause an error and issue BMC47359 OPTION IS NOT ALLOWED FOR REALDD.

When you specify a value for REALDD and specify STACK YES, BMC AMI Copy always uses the REALDD value.

Warning

You should not reference the same DD statement from two different OUTPUT statements.

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 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.

TRTCH

Specify TRTCH when you want to define tape data compression for the named descriptor. Use TRTCH COMP to provide tape data compression. Use TRTCH NOCOMP to prevent data compression. TRTCH NONE is the BMC AMI Copy default and specifies that you want to use the MVS default. If you do not specify TRTCH, BMC AMI Copy uses the value of the TRTCH installation option.

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

RETPD integer

Specify RETPD integer in the descriptor named after the OUTPUT keyword to set a new retention period (in days) for the current copy data set. If you do not specify RETPD, the retention period defaults to the value (if any) of the RETPD installation option.

The value of integer must be in the range 1 through 9999.

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

Important

When EXPDT is specified on the OUTPUT statement, it takes precedence over RETPD. However, if EXPDT is not specified on the OUTPUT statement and RETPD is specified on the OUTPUT statement, RETPD overrides EXPDT in the installation options module.

EXPDT date

Specify EXPDT date in the descriptor named after the OUTPUT keyword to set a new expiration date for the current copy data set. If you do not specify EXPDT, the expiration date defaults to the value of the EXPDT installation option. The default value of the EXPDT installation option is 99000.

Important

When it is specified on the OUTPUT statement, EXPDT takes precedence over RETPD. However, if EXPDT is not specified on the OUTPUT statement and RETPD is specified on the OUTPUT statement, RETPD overrides EXPDT in the installation options module.

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.

 

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