OPTIONS syntax option description

The following options are available for the OPTIONS command:

Option

Description

AUX

The AUX option allows BMC AMI Copy to include auxiliary objects and history objects in the copy without having to explicitly specify these objects.

The AUX option is available on the OPTIONS, COPY, COPY IMAGECOPY, and EXPORT commands. If you do not specify AUX on one of these commands, BMC AMI Copy uses the value of the AUX installation option (AUX=NO) as the default value.

Valid values are NO, ALL, XML, and LOB.

Important

The AUX option is ignored if you specify RMGROUP, RMGROUPTS, RMGROUPIX, or OBJECTSET.

AUX values

Value	Description
NO	If you specify AUX NO, BMC AMI Copy does not include auxiliary objects or objects related by a history (versioning) relationship to the originally specified objects in the copy. You may include HISTORY objects with the HISTORY keyword. See HISTORY below.
ALL	If you specify AUX ALL, BMC AMI Copy includes XML and LOB objects for the base table space. It does not include any system-time base tables with their related HISTORY tables. You may include HISTORY objects with the HISTORY keyword. See HISTORY below.
XML	If you specify AUX XML, BMC AMI Copy includes only XML auxiliary objects with the XML base space in the copy. You can include indexes for the auxiliary spaces and history spaces by specifying INDEXES YES. BMC AMI Copy supports AUX XML on the OPTIONS, COPY, or COPY IMAGECOPY commands. If you specify AUX XML on the EXPORT command, BMC AMI Copy issues the following message: BMC47427I AUX XML IS NOT SUPPORTED. For more information, see Using-BMC-AMI-Copy-for-XML-objects.
LOB	If you specify AUX LOB, BMC AMI Copy includes only LOB auxiliary objects with the LOB base space in the copy. You can include indexes for the auxiliary spaces by specifying INDEXES YES.

HISTORY

If you specify HISTORY with AUX, and include a space containing a system-period temporal table in the copy command, either explicitly or by wildcard, BMC AMI Copy includes the space containing the associated history table in the copy. You may include the indexes by specifying INDEXES YES.

ARCHIVE

If you specify ARCHIVE with AUX, BMC AMI Copy copies archive tables.

You must specify AUX to use the ARCHIVE keyword. The meaning of the ARCHIVE keyword depends on the AUX option specified, as follows:

AUX NO ARCHIVE (or AUX ARCHIVE) includes archive-enabled base tables and their related archive tables. It does not include related XML or LOB objects.
AUX ALL ARCHIVE includes archive-enabled base tables and their related archive tables, and all related XML and LOB objects.
AUX XML ARCHIVE includes archive-enabled base tables and their related archive tables, and all related XML objects.
AUX LOB ARCHIVE includes archive-enabled base tables and their related archive tables, and all related LOB objects.

Important

Ensure that you specify the HISTORY option before the AUX HISTORY option.

COMPRESS

Use this option to override the value of the COMPRESS installation option (COMPRESS=NO) that tells BMC AMI Copy whether to compress disk image copies.

This option provides synergy with the BMC PACLOG utility by using the BMC Extended Compression Architecture (XCA) technology. The compressed disk image copies can be used by the IBM Db2 BMC AMI Recover and DSN1COPY utilities and the BMC AMI Recover and UNLOAD PLUS utilities. This option can also be set with the COPY command (see COPY-command).

To enable compression, the PACLOGload library must be in the BMC AMI Copy STEPLIB or JOBLIB. See the PACLOG for DB2 documentation for more details.

If you do not specify COMPRESS in the OPTIONS command, BMC AMI Copy uses the value of the COMPRESS installation option as the default.

Important

COMPRESS is ignored for Instant Snapshots.

Compress values

Value

Description

YES

Specifying COMPRESS YES tells BMC AMI Copy to compress disk image copies. COMPRESS YES can be used in conjunction with the SQUEEZE YES of the COPY and COPY IMAGECOPY commands for additional savings.

If COMPRESS YES is specified but the compression libraries are not available or there is a problem registering the data set, a warning is issued and the copy continues without compression.

If COMPRESS YES is specified and the data set being copied is on tape, an informational message is issued to indicate that compression will not be invoked.

Specifying COMPRESS NO tells BMC AMI Copy not to use compression for disk image copies.

DATAMVR programName

The DATAMVR option provides XBM with the name of the program to use to copy a data set if an Instant Snapshot (DSSNAP YES) fails. To use DFDSS as the data mover, specify DATAMVR ADRDSSU.

If you do not specify DATAMVR on the OPTIONS command, BMC AMI Copy uses the value of the DATAMVR installation option (DATAMVR=) as the default.

DB2NTRY integer

Use this option to override the value of the DB2NTRY installation option (DB2NTRY=10) that tells BMC AMI Copy the maximum number of times to attempt to use a resource before concluding that the resource can not be obtained. The value of integer can be any integral value from 1 through 255. DB2NTRY applies to both COPY and COPY IMAGECOPY executions.

If you do not specify DB2NTRY with the OPTIONS command, BMC AMI Copy uses the value of the DB2NTRY installation option as the default.

DB2WAIT integer

Use this option to override the value of the DB2WAIT installation option (DB2WAIT=3) that specifies the time that BMC AMI Copy is to wait (in seconds) between attempts to use the following Db2 resources when they are not immediately available:

The Db2 system catalog
The BMCUTIL, BMCSYNC, or BMCXCOPY tables
The IBM Db2 COPY utility
The table space being copied

When any of these resources are under the control of another process and not available, BMC AMI Copy waits for the number of seconds specified by DB2WAIT and then attempts to use the resource again. BMC AMI Copy repeats the attempt up to the number of times specified by DB2NTRY before concluding that the resource can not be obtained.

The value of integer can be any integer value from 1 through 655. Note that the waiting time specified by DB2WAIT is additional to Db2 resource timeout and utility values IRLMRWT and UTIMOUT set in DSNZPARM.

The formulas given below are used to determine the total amount of time that BMC AMI Copy will wait between attempts to use the resources listed above and the execution of a command.

For IBM Db2 COPY commands (QUIESCE, REPAIR, or COPY):
(IRLMRWT * UTIMOUT) + DB2WAIT
For SQL commands:
IRLMRWT + DB2WAIT
For Db2 commands (STOP, START, and DISPLAY):
DB2WAIT

The total amount of time BMC AMI Copy will wait is the product of DB2NTRY and result of the formulas above.

If you do not specify DB2WAIT in the OPTIONS command, BMC AMI Copy uses the value of the DB2WAIT installation option as the default.

DB2WAIT applies to both COPY and COPY IMAGECOPY executions.

DISPLOCK

Use this option to override the value of the DISPLOCK installation option ( DISPLOCK=NO ) that indicates whether BMC AMI Copy is to use DISPLAY LOCKS to determine group buffer pool dependence when using SHRLEVEL CHANGE and data sharing.

If you do not specify DISPLOCK on the OPTIONS command, BMC AMI Copy uses the value of the DISPLOCK installation option as the default.

Important

If you expect a large number of locks, we recommend that you specify DISPLOCK NO for BMC AMI Copy. (DISPLOCK=NO is the installation option default value.) Failures due to a large number of locks are characterized by message BMC30567.

DISPLOCK values

Value	Description
YES	Specifying DISPLOCK YES tells BMC AMI Copy to use DISPLAY LOCKS to determine group buffer pool dependence when using SHRLEVEL CHANGE and data sharing.
NO	Specifying DISPLOCK NO tells BMC AMI Copy to avoid issuing DISPLAY LOCKS and use a different internal technique to determine the group buffer pool dependency. If a job specifies DISPLOCK=NO and a member of a data sharing group is in FAILED status, BMC AMI Copy issues the DISPLAY LOCKS command, regardless of the DISPLOCK specification. Doing so allows BMC AMI Copy to evaluate the space and bypass a quiesce in most cases. However, if the failed member does hold retained locks on the space BMC AMI Copy is attempting to copy, BMC AMI Copy will fail.
ONLY	Specifying DISPLOCK ONLY tells BMC AMI Copy to use the DISPLAY LOCKS ONLY command to only display spaces that have locks.

DFDSSASN

The DFDSSASN option lets you specify the DFDSS address space. You can specify a value for this option to use multiple DFDSS servers when you make Flash Copies. The value can have up to 8 characters. If you do not specify a value for this option, the system default name for the DFDSS server and a single server are used.

DFDSSNS

The DFDSSNS option lets you use multiple DFDSS servers when you make Flash Copies. You must reassemble the installation options module when you specify a new value for DFDSSNS. If you do not reassemble the module, the default value, 1, is used.

DRAINWAIT

Specifies the number of seconds to wait when it drains the table space or index

The valid value ranges from 1 through 1800. The default value is 20

DRAINRETRY

Specifies the maximum number of retries to attempt

The valid value ranges from 0 through 999. The default value is 100

DRAINDELAY

Specifies the minimum duration, in seconds, between retries

The valid value ranges from 1 through 1800. The default value is 100

FULLRESET

This option changes SHRLEVEL CHANGE RESETMOD NO copies to use RESETMOD YES if BMC AMI Copy makes full copies when you use FULL AUTO or CHANGELIMIT.

FULLRESET has no effect with other values of SHRLEVEL.

Important

FULLRESET does not support resetting the modification indicators for LOB spaces because BMC AMI Copy makes efficient incremental copies of LOBs without using the modification indicators.
You can also specify FULLRESET on the COPY command.

If you do not specify FULLRESET on the OPTIONS command, BMC AMI Copy uses the value of the FULLRESET installation option ( FULLRESET=NO ) as the default.

FULLRESET values

Value

Description

YES

When you specify SHRLEVEL CHANGE RESETMOD NO and FULL AUTO RESETMOD NO or CHANGELIMIT RESETMOD NO, specifying FULLRESET YES changes full copies to use RESETMOD YES. BMC AMI Copy invokes DSNUTILB to make the full copy if the option SLCHGRESET NO is specified. When the full copies use RESETMOD YES, subsequent FULL AUTO or CHANGELIMIT jobs will be able to accurately determine the number of changed pages, which can prevent the unnecessary selection of a full copy.

When you specify SHRLEVEL CHANGE RESETMOD NO and FULL AUTO RESETMOD NO or CHANGELIMIT RESETMOD NO, specifying FULLRESET NO does not convert copies to use RESETMOD YES when BMC AMI Copy makes full copies.

HISTORY

The HISTORY option enables you to choose whether to insert a utility history row into the BMCHIST table to record information about completed BMC AMI Copy executions.

History values

Value	Description
NO	(Default) Bypasses the insert and records no information
YES	Inserts detailed information into the BMCHIST table about the BMC AMI Copy execution
SUMMARY	Inserts only summary information into the BMCHIST table about the BMC AMI Copy execution. This option provides less information than the YES option.

Important

Ensure that you specify the HISTORY option before the AUX HISTORY option.

See Common-utility-tables for the contents of the BMCHIST table.

HISTRETN integer

Use this option to override the value of the HISTRETN installation option (HISTRETN=0) that specifies the number of days BMC AMI Copy is to keep entries in the BMC history table (BMCHIST) before deleting them.

Deletions are based on the DBNAME, SPNAME, UTILNAME and DATE columns in the history table. BMC AMI Copy deletes entries older than integer days. Valid values for HISTRETN are 0-999.

If you do not specify HISTRETN with the OPTIONS command, BMC AMI Copy uses the value of the HISTRETN installation option as the default. The installation option default is HISTRETN=0, which specifies that BMC AMI Copy is not to delete any rows.

Example HISTRETN values and their meanings:

HISTRETN=0 means do not attempt to delete any rows.
HISTRETN=1 means delete all rows older than 1 day back (yesterday).
HISTRETN=2 means delete all rows older than 2 days back.

In other words, rows for today and yesterday cannot be deleted until tomorrow.

INVCACHE

Use this option to override the value of the INVCACHE installation option (INVCACHE=NO) that specifies whether to invalidate the dynamic SQL statement cache when you make image copies by using the RUNSTATS YES option.

INVCACHE values

Value

Description

If you specify INVCACHE NO, BMC AMI Copy does not invalidate the dynamic SQL statement cache.

YES

If you specify INVCACHE YES, BMC AMI Copy invalidates statements in the dynamic statement cache when you use the RUNSTATS option in the COPY command against objects to which those statements refer. Invalidating the cached statements ensures that the plans created from the dynamic SQL will be recreated with new statistics the next time that they are executed so that any access path changes are picked up.

IXDSNUM

Use this option to override the value of the IXDSNUM installation option (IXDSNUM=ALL) that determines the way BMC AMI Copy interprets DSNUM for indexes and makes the index copies, using either the COPY TABLESPACE, INDEXES YES, or the COPY INDEXSPACE command.

If you do not specify IXDSNUM on the OPTIONS statement, BMC AMI Copy uses the value of the IXDSNUM installation option.

Important

If you are working with COPY YES indexes, we recommend that you set IXDSNUM=ALL.

IXDSNUM values

Value

Description

DATASET

Specifying IXDSNUM DATASET with either COPY TABLESPACE ... INDEXES YES or COPY INDEXSPACE tells BMC AMI Copy to copy indexes as shown in Evaluation of DSNUM with IXDSNUM DATASET.

ALL

Specifying IXDSNUM ALL tells BMC AMI Copy to copy indexes as shown in Evaluation of DSNUM with COPY INDEXSPACE IXDSNUM ALL and Evaluation of DSNUM with COPY TABLESPACE ... INDEXES YES IXDSNUM ALL .

Important

The difference between the use of COPY INDEXSPACE and COPY TABLESPACE ... INDEXES YES with IXDSNUM ALL is in the handling of a nonpartitioning index using DSNUM integer. For COPY INDEXSPACE, DSNUM integer is interpreted as data set integer. For COPY TABLESPACE ... INDEXES YES, DSNUM integer is interpreted as DSNUM ALL.

Evaluation of DSNUM with IXDSNUM DATASET

DSNUM value specified ¹	DSNUM for nonpartitioning index	DSNUM for partitioning index
ALL	Data set 1 through the last data set	Partition number 1 through the last partition number
PART	Data set 1 through the last data set	Partition number 1 through the last partition number
DATASET or not specified	Data set 1 through the last data set	Partition number 1 through the last partition number
n where n is an integer value	Data set 1 through the last data set	Partition number n

^{1 This DSNUM value applies to index copies only—not table space copies.}

Evaluation of DSNUM with COPY INDEXSPACE IXDSNUM ALL

DSNUM value specified ¹	DSNUM for nonpartitioning index	DSNUM for partitioning index
ALL or not specified	ALL	ALL
PART	ALL	Partition number 1 through the last partition number
DATASET	Data set 1 through the last data set	Partition number 1 through the last partition number
n where n is an integer value	n	Partition number n

_{1 This DSNUM value applies to index copies only—not table space copies.}

Evaluation of DSNUM with COPY TABLESPACE ... INDEXES YES IXDSNUM ALL

DSNUM value specified ¹	DSNUM for nonpartitioning index	DSNUM for partitioning index
ALL or not specified	ALL	ALL
PART	ALL	Partition number 1 through the last partition number
DATASET	data set 1 through the last data set	Partition number 1 through the last partition number
n where n is an integer value	ALL	Partition number n

_{1 This DSNUM value applies to index copies only—not table spaces copies.}

IXEXPAND

Use this option to override the value of the IXEXPAND installation option (IXEXPAND = AUTO) that specifies how BMC AMI Copy handles compressed indexes. For more information, see Copying-compressed-indexes.

IXEXPAND values

Value	Description
AUTO	IXEXPAND AUTO, which is the installation option default value, indicates that BMC AMI Copy checks to see if you are using a Recovery Management for Db2 password to determine how to make copies of compressed index. See IXEXPAND NO. if you are using Recovery Management for Db2, BMC AMI Copy copies the compressed indexes, without expanding them, and registers the copy in BMCXCOPY. See IXEXPAND YES, if you are not using Recovery Management for Db2, BMC AMI Copy expands the compressed indexes before copying them and registers the copy in SYSCOPY.
YES	IXEXPAND YES specifies that BMC AMI Copy expands compressed indexes before copying them and registers the copy in SYSCOPY. This copy is compatible with the IBM Db2 COPY utility. However, some BMC copy techniques, such as Instant Snapshots and online consistent copies, are not supported if you specify IXEXPAND YES. Important If you specify IXEXPAND YES and request a copy that BMC AMI Copy cannot decompress, such as an Instant Snapshot, BMC AMI Copy makes a compressed copy and issues an informational message.
NO	IXEXPAND NO specifies that BMC AMI Copy copies the compressed indexes without expanding them and registers the copy in BMCXCOPY. You can use this copy for recovery only with the BMC AMI Recover product. All BMC AMI Copy copy techniques are supported. However, BMC AMI Copy does not copy compressed indexes of the Db2 catalog and directory when you specify IXEXPAND NO because BMC AMI Recover cannot recover them.

IXSIZE

Use this option to override the value of the IXSIZE installation option (IXSIZE=0) that specifies a size threshold for making index copies. Unless this threshold is met or exceeded, no index copy is made. (The installation option default value is 0, which means this option has no effect.)

IXSIZE can be specified as number of pages. Valid values for number of pages are 0 through 1,073,741,823 and is specified as IXSIZE integer.

You can also specify IXSIZE specified in kilobytes, megabytes, or gigabytes as follows:

IXSIZE integer K, with a limit of 4,294,967,295
IXSIZE integer M, with a limit of 4,194,303
IXSIZE integer G, with a limit of 4095

The IXSIZE threshold is ignored if any output does not use dynamic allocation.

MAXTASKS (tapeTasks[,totalTasks])

Use this option to override the value of the MAXTASKS installation option (MAXTASKS=(1,AUTO)) that controls the number of subtasks used by BMC AMI Copy when making GROUP YES or GROUP NO copies.

MAXTASKS applies to COPY TABLESPACE, COPY INDEXSPACE, and COPY INDEX executions.

In the MAXTASKS syntax, the tapeTasks value is required, the brackets ([ ]) indicate that the totalTasks value is optional, and the parentheses are also optional.

The tapeTasks value controls the number of tape units to use concurrently. The totalTasks value indicates the total number of subtasks that BMC AMI Copy can use. If BMC AMI Copy does not use all subtasks indicated by the tapeTasks value for tape processing, BMC AMI Copy can use the unused subtasks for disk processing.

The default values are 1 for tapeTasks and AUTO for totalTasks. AUTO allows BMC AMI Copy to determine the value for totalTasks. Valid values for tapeTasks are 1 through 32. Valid values for totalTasks are tapeTasks through 32.

To enable tape subtasks only, specify tapeTasks equal to totalTasks. For example, specify MAXTASKS n, n. You can also specify simply MAXTASKS n, which is the same as MAXTASKS n, n. In this case, each tape task would have its own stacked tape.

Otherwise, the value of tapeTasks should be less than the value of totalTasks. If you do not want BMC AMI Copy to perform subtasking, specify MAXTASKS (1,1), and BMC AMI Copy will do all work in the main task.

When you use multitasking, each task can have a DD statement with the naming convention ACPPRTnn where nn is the task number, 01 through 32. If the DD statement is not present, BMC AMI Copy dynamically allocates the ACPPRTnn data sets to SYSOUT.

For more information about MAXTASKS, see Specifying-multitasking.

Important

Multitasking might require changes to the following DB2 DSNZPARMS:

CTHREAD (maximum users)
IDFORE (maximum users from TSO)
IDBACK (maximum number of concurrent attachments from batch)

MIGRSKIP

Use this option to override the value of the MIGRSKIP installation option (MIGRSKIP=NO) that indicates whether BMC AMI Copy is to skip spaces that have been archived or migrated.

If you do not specify MIGRSKIP on the OPTIONS command, BMC AMI Copy uses the value of the MIGRSKIP installation option as the default.

MIGRSKIP values

Value	Description
NO	Specifying MIGRSKIP NO tells BMC AMI Copy to not skip migrated or archived spaces.
YES	Specifying MIGRSKIP YES tells BMC AMI Copy to skip spaces that have been migrated or archived. MIGRSKIP YES does not apply to spaces having more than one part and DSNUM ALL.

MIGRVOL volumeID

Use this option to override the value of the MIGRVOL installation option ( MIGRVOL= ) that allows you to identify an additional volume used for migration. BMC AMI Copy recognizes MIGRAT and ARCIVE. If you do not specify MIGRVOL on the OPTIONS command, BMC AMI Copy uses the value of the MIGRVOL installation option as the default.

NBRBUFS integer

Use this option to override the value of the NBRBUFS installation option (NBRBUFS=4) that specifies how many read/write buffers BMC AMI Copy is to use and manage. Valid values for integer are 2 through 16. NBRBUFS applies to both COPY and COPY IMAGECOPY executions.

More buffers allow additional read and write ahead capability. However, more buffers require more memory (up to 737280 bytes per buffer) and, because more buffer management is required, additional CPU usage occurs. Also, read/write buffers must be fixed in memory for the duration of the read or write operations.

For more information about how NBRBUFS can affect BMC AMI Copy performance, see BMC-AMI-Copy-read-and-write-buffers-NBRBUFS.

If you do not specify NBRBUFS, BMC AMI Copy uses the value of the NBRBUFS installation option as the default.

Important

BMC AMI Copy read/write buffers are not QSAM or BSAM buffers, which are specified by the BUFNO value of a DCB parameter of a DD statement.

OUTSIZE

Use this option to override the value of the OUTSIZE installation option (OUTSIZE=0) that specifies a size threshold for making copies to an alternate DD or output descriptor and can be used to escalate output to tape rather than DASD, or to Instant Snapshots, rather than standard copies. (The installation option default value is 0, which means this option has no effect.)

OUTSIZE can be specified as the number of physical pages. Valid values for number of pages are 0 through 1,073,741,823. This can be specified as OUTSIZE integer or as OUTSIZE integer P.

OUTSIZE can also be specified in kilobytes, megabytes, or gigabytes as follows:

OUTSIZE integer K, with a limit of 4,294,967,295
OUTSIZE integer M, with a limit of 4,194,303
OUTSIZE integer G, with a limit of 4095

If a value greater than 0 is specified and the estimated size of the resulting copy for the space or partition being copied is less than the value specified with OUTSIZE, the image copy goes to the DDs as normal (using COPYDDN, RECOVERYDDN, COPYDSN, RECOVERYDSN, FULLDDN, FULLRECDDN, FULLDSN, or FULLRECDSN if specified). If the threshold specified for OUTSIZE is met or exceeded by the estimated size of the resulting copy, the image copy output will go to an alternate set of DDs that are specified with the following keywords (described on BIGDDN through FULLRECDSN):

BIGDDN
BIGDSN
BIGRECDDN
BIGRECDSN

OUTSIZE requires the use of dynamic allocation and can be used with any FULL option. BMC AMI Copy analysis determines the estimated size of the resulting copy and compares this estimated value to the OUTSIZE value.

READONLY

Use this option to override the value of the READONLY installation option (READONLY=STARTRO) that specifies how BMC AMI Copy is to set the space status while initializing the connection to XBM in preparation for making SHRLEVEL CONCURRENT copies.

For a more detailed discussion of the impact of using READONLY STARTRO and READONLY LOCKTBL, see Making-SHRLEVEL-CONCURRENT-copies-Snapshot-Copies.

READONLY values

Value	Description
STARTRO	READONLY STARTRO tells BMC AMI Copy to always set the space status to RO while initializing the connection to XBM in preparation for making SHRLEVEL CONCURRENT copies. Note BMC AMI Copy always sets the space status to RO when any of the following situations apply: The space is a Db2 catalog and directory space. The space is in COPY-pending status. The space or any partition is in UT status.
LOCKTBL	READONLY LOCKTBL tells BMC AMI Copy to use LOCK TABLE while initializing the connection to XBM in preparation for making SHRLEVEL CONCURRENT copies. READONLY LOCKTBL does not allow operation at the partition level and results in the entire table space being locked.
DRAIN	READONLY DRAIN blocks all new updaters and completes the current updaters. You can specify the maximum amount of time to wait for the drain to complete. If the DRAINWAIT value is less than the DB2 IRLMRWT value (default 30 seconds), the application does not time out, thus improving data availability. Notes You can use the DRAINWAIT, DRAINRETRY, and DRAINDELAY options to adjust the behavior of the DRAIN in READONLY. You must have installed BMC AMI Utilities

REGISTEROCC

( SPE2104 )

Use this option to register online consistent copy (OCC) like a consistent FlashCopy copy in SYSCOPY, when possible. IBM RECOVER can use these copies directly. Copies such as LB, RP, and RB, which cannot be registered as FlashCopy, continue to be registered in BMCXCOPY.

The REGISTEROCC option is available in both the installation default options and in SYSIN.

REGISTEROCC values

Value	Description
BMCXCOPY	(Default) The OCC is registered in BMCXCOPY and is used by BMC AMI Recover . It cannot be used directly by IBM RECOVER.
SYSCOPY	If you specify SYSCOPY, an LP OCC is registered in SYSCOPY and can be used directly by IBM RECOVER.

SLCHGRESET

Use this option to specify how to process SHRLEVEL CHANGE RESETMOD YES copies.

SLCHGRESET YES offers an advantage over SHRLEVEL CHANGE RESETMOD YES. SLCHGRESET YES resets the modification indicators except for pages that might have updates in the Db2 buffer pool. SLCHGRESET YES is more efficient than IBM Db2 COPY, because it does not get Db2 locks or latches and does not cause contention with other applications.

SLCHGRESET values

Value

Description

YES

BMC AMI Copy makes native SHRLEVEL CHANGE RESETMOD YES copies.

To enable native support for SHRLEVEL CHANGE RESETMOD YES, BMC AMI Copy uses the XBM feature that monitors Db2 space map updates. The XBM feature that monitors Db2 space map updates uses software snapshot processing. Therefore, you must ensure that the appropriate management set and configuration have been created and activated in XBM or SUF. For more information, see the SNAPSHOT UPGRADE FEATURE for DB2 documentation.

Note

If SLCHGRESET YES is specified, RESETMOD YES is ignored for CUMULATIVE incremental copies.

BMC AMI Copy invokes DSNUTILB for SHRLEVEL CHANGE RESETMOD YES copies.

SMARTSTACK

Use this option to override the value of the SMARTSTK installation option (SMARTSTK=YES) that specifies if BMC AMI Copy is to stack incremental copies in the same logical stacking order as their associated full copies.

If you do not specify SMARTSTACK on the OPTIONS command, BMC AMI Copy uses the value of the SMARTSTK installation option as the default.

Note

SMARTSTACK can also be specified on the COPY command.

SMARTSTACK values

Value	Description
YES	BMC AMI Copy analyzes the stacking order for the associated full copies and stacks the incremental copies in the same order. SMARTSTACK YES requires the use of grouping.
NO	BMC AMI Copy does not perform stacking analysis for incremental copies. Incremental copies are stacked as they are processed.

SNAP

This option indicates how BMC AMI Copy should make VSAM copies when DSSNAP YES is specified. BMC AMI Copy can make VSAM copies even if the data sets are not on a snappable disks.

If you do not specify SNAP on the OPTIONS command, BMC AMI Copy uses the value of the SNAP installation option by default. The default value of the SNAP installation option is HW.

SNAP values

Value

Description

( SPE2010) When you specify SNAP HW, BMC AMI Copy calls XBM to make an Instant Snapshot by using the hardware data set snapshot capability. If the data sets are not snappable, the copy fails unless a DATAMVR is specified. SNAP=HW supports both SMS-managed and non-SMS-managed data sets.

VSAM

( SPE2010) When you specify SNAP VSAM, BMC AMI Copy calls DFSMSdss to copy a VSAM data set by using conventional I/O if the source or target is not on snappable disk. If the data sets are on a snappable disks, BMC AMI Copy uses fast replication. If a DATAMVR is specified, BMC AMI Copy uses FAST REPLICATION PREFERRED. If a DATAMVR is not specified, Copy uses FAST REPLICATION REQUIRED. You can use the following example syntax when you specify SNAP=VSAM:

OPTIONS SNAP VSAM
   DATAMVR DFDSS

OUTPUT LOCALP
   DSSNAP YES
   DSNAME dataSetName

COPY TABLESPACE tableSpaceName
   DSNUM DATASET

SOFTQUIESCE

( SPE2005 )

Use this option to perform a quiesce by DRAIN instead of Db2 QUIESCE.

SOFTQUIESCE is available only if the following conditions exist:

You have installed an BMC AMI Utilities utility.
The BMC AMI Utilities load library is in the STEPLIB and LINKLIB.

Note

(SPE2104) SOFTQUIESCE now supports SHRLEVEL REFERENCE.

SOFTQUIESCE values

Value

Description

YES

By specifying YES:

BMC AMI Copy uses DRAIN option instead of IBM Db2 QUIESCE if you specify one of the following options:

QUIESCE BEFORE—for more information, see QUIESCE-BEFORE-and-QUIESCE-AFTER
QUIESCE AFTER— for more information, see QUIESCE-BEFORE-and-QUIESCE-AFTER
QUIESCE command options—for more information, see QUIESCE-command
BMC AMI Copy can operate at the partition level.
If you specify the DRAINWAIT value to be less than the lock timeout:
- Application impact is minimized.
- Update attempts should not fail.

(Default)

BMC AMI Copy

uses IBM Db2 QUIESCE.

Note

You can use the DRAINWAIT, DRAINRETRY, and DRAINDELAY options to adjust the behavior of the DRAIN in SOFTQUIESCE.

SUPPRESS messageNumberList

Use this option to suppress output messages. Suppressing messages is usually done for page checking errors but is also done to limit print output. The SUPPRESS option is also used to omit warning messages produced by CHECKTSLEVEL processing.

Warning

Suppressing messages might impair the ability to identify or resolve problems.

The SUPPRESS option is followed by one or more message numbers separated by commas.

Example

OPTIONS SUPPRESS 47440, 47466, 47422
COPY TABLESPACE ACP*.*

The message numbers specified do not print to SYSPRINT or ACPPRT nn. For page checking messages whose severity is controlled by the CHECKERROR option on the COPY or COPY IMAGECOPY commands or the CHECKERR installation option, the return code is also suppressed.

Message numbers must be within the BMC AMI Copy message ranges, but will not be validated as E, I, W, or U message types until the messages are issued. Message type E messages are not suppressed.

SYSBACKUP

Use this option to specify whether image copies derived from system-level backups will be considered by COPY IMAGE COPY.

If you do not specify SYSBACKUP on the OPTIONS command, BMC AMI Copy uses the value of the SYSBACKUP installation option as the default value. The default value of the SYSBACKUP installation option is NO.

SYSBACKUP values

Value	Description
YES	BMC AMI Copy COPY IMAGECOPY command includes image copies derived from system-level backups in the set of candidate image copies.
NO	BMC AMI Copy COPY IMAGECOPY command does not include image copies derived from system-level backups in the set of candidate image copies.

UPDATECLRSN

( SPE2005 )

Use this option to update the CLRSN. The CLRSN must be updated in order to reset COPYUPDATEDPAGES.

You might want to update the CLRSN in the following scenarios:

You specify FULL AUTO, because specifying FULL AUTO causes BMC AMI Copy to use the COPYUPDATEDPAGES value to determine the timing and type of copy.
You need to obtain an accurate COPYUPDATEDPAGES value.

Best practice
Updating the CLRSN involves a significant overhead, so if you never use FULL AUTO and the accuracy of COPYUPDATEPAGES is not important for small spaces, we recommend using UPDATECLRSN YES.

UPDATECLRSN values

Value	Description
YES	(Default) Updates the CLRSN for large (greater than 200 megabytes) spaces with changes
NO	Never updates the CLRSN
ALL	Updates the CLRSN for all spaces with changes

WORKPREFIX prefix

This option provides BMC AMI Copy with a high-level qualifier to use in creating temporary data sets. If you do not specify WORKPREFIX on the OPTIONS command, BMC AMI Copy uses the value of the WORKPREFIX installation option as the default.

XBMID ssid or xbmGroup

Use this option to override the value of the XBMID installation option (XBMID= ssid or xbmGroup). Specify the XBM or SUF ssid or xbmGroup name to be active when using XBM or SUF with BMC AMI Copy. BMC AMI Copy uses the XBMID when you:

Make SHRLEVEL CONCURRENT (standard Snapshot) copies
Make Instant Snapshot copies
Use the XBM Utility Monitor
Want to use a specific XBM subsystem for zIIP processing

ssid is the unique identifier that was specified when XBM or SUF was installed. If you are using XBM or SUF in a Db2 data sharing environment, you can use the xbmGroup name instead of ssid. The xbmGroup name is the name of the cross-system coupling facility (XCF) group that is defined to the XBM subsystem.

Note

BMC AMI Copy supports only alphanumeric characters for the specification of XBMID. If you use the wildcard characters ', ?, @, %, or . in the XBMID installation option, the assembly of the options table fails with rc=8 and issues the following message:

A NGT COPY XBMID CANNOT CONTAIN A character CHARACTER

For standard Snapshot copies, you can specify XBMID with either of the following commands or options:

On the OPTIONS command
With SHRLEVEL CONCURRENT on the COPY command

However, for Instant Snapshot copies, you must specify XBMID on the OPTIONS command.

For use of XBMID with SHRLEVEL CONCURRENT on the COPY command to make standard Snapshot copies, see Making-SHRLEVEL-CONCURRENT-copies-Snapshot-Copies.

If you specify an XBM subsystem and ZIIP ENABLED is in effect, BMC AMI Copy attempts to use that subsystem to enable zIIP processing. If that subsystem is not available or if it is not at the correct maintenance level, zIIP processing is not enabled.

If you do not specify an XBM subsystem either here or with the XBMID option on the OPTIONS command, BMC AMI Copy searches for an XBM subsystem at the appropriate maintenance level to enable zIIP processing.

If you do not specify XBMID, BMC AMI Copy uses the value of the XBMID installation option (XBMID= ssid or xbmGroup) as the default.

For more information about Snapshot Copies, Instant Snapshots, the Utility Monitor, and the use of zIIPs, see the SNAPSHOT UPGRADE FEATURE for DB2 documentation.

XBMMNTR

Use this option to override the value of the XBMMNTR installation option (XBMMNTR=NO) that indicates if BMC AMI Copy is to use the XBM Utility Monitor. The XBM Utility Monitor is a feature of the BMC EXTENDED BUFFER MANAGER (XBM) or SNAPSHOT UPGRADE FEATURE (SUF) product. One of these products must be properly installed to use the Utility Monitor. The XBM Utility Monitor displays status information about your copy job as it is running including:

Job name
Date and time
Step name
The number of the copy command being executed
The number of data sets processed
The names of the data sets processed

If you are using wildcards or GDGs, they will be expanded and each data set name will be given as it is processed. If you are copying a group, each name in the group will be given as it is processed.

If you do not specify XBMMNTR, BMC AMI Copy uses the value of the XBMMNTR installation option as the default.

XBMMNTR values

Value	Description
NO	Specifying XBMMNTR NO tells BMC AMI Copy that the XBM Utility Monitor will not be used.
YES	Specifying XBMMNTR YES tells BMC AMI Copy to use the XBM Utility Monitor. Note See the SNAPSHOT UPGRADE FEATURE for DB2 documentation for more information about the Utility Monitor.

XBMRSTRT

Use this option to override the value of the XBMRSTRT installation option (XBMMNTR=NO) that indicates whether copies made with SHRLEVEL CONCURRENT specified are restartable in the COPY phase should an BMC AMI Copy job fail.

For restartable Snapshot Copies, you must be using XBM version 3.0 or later.

If you do not specify XBMRSTRT, BMC AMI Copy uses the value of the XBMRSTRT installation option as the default.

XBMRSTRT values

Value

Description

Copies made with SHRLEVEL CONCURRENT specified restart in the UTILINIT phase, copying all specified spaces.

YES

Copies made with SHRLEVEL CONCURRENT specified restart in the COPY phase with the space where BMC AMI Copy failed.

For Snapshot Copies, the SNAPSHOT UPGRADE FEATURE continues to cache the data sets and allows BMC AMI Copy to continue on restart where it left off instead of restarting in the UTILINIT phase.

Note

Since the SNAPSHOT UPGRADE FEATURE continues to run and cache after an BMC AMI Copy failure, restarting BMC AMI Copy soon after the failure reduces the size of cache.

XCOPYDEL

Use this option to delete orphaned rows from BMCXCOPY. Orphaned rows are entries that exist on BMCXCOPY but represent objects that have been dropped from the IBM Db2 catalog.

You can use the XCOPYDEL option only with a MODIFY command because the MODIFY code deletes the orphaned rows. The TABLESPACE listed on the MODIFY command must be a valid Db2 object, but the TABLESPACE has no bearing on the orphaned rows interrogated in BMCXCOPY.

The OPTIONS command overrides the assembled options module.

On the first MODIFY encountered, when XCOPYDEL YES or XCOPYDEL LIST is coded on the OPTIONS command, BMCXCOPY is interrogated first, before the MODIFY command, to see if any orphans exist.

XCOPYDEL values

Value	Description
NO	BMC AMI Copy does not delete orphaned rows from BMCXCOPY. XCOPYDEL NO is the default value.
YES	BMC AMI Copy deletes orphaned rows from BMCXCOPY when the Db2 object is dropped and no longer exists. XCOPYDEL YES removes the orphans, including performing ICFDELETE of the image copy data sets. The standard ICFDELETE option is not required.
LIST	BMC AMI Copy lists the orphaned rows in BMCXCOPY that you can delete with XCOPYDEL YES. No rows are deleted from BMXCOPY. XCOPYDEL LIST lists the orphan rows. After the orphan rows are processed, the MODIFY command continues as specified with the syntax provided. Subsequent MODIFY statements do not trigger the cleanup again because the cleanup code runs once, when the first MODIFY command is encountered.

ZIIP

This option tells BMC AMI Copy whether to attempt to use IBM System z Integrated Information Processors (zIIPs). BMC AMI Copy can use enclave service request blocks (SRBs) to enable zIIP processing automatically while running jobs. Using zIIP processing can reduce the overall CPU time for BMC AMI Copy jobs.

Tip

When you use zIIP processing, we recommend that you set IIPHONORPRIORITY=YES in the IEAOPT member of SYS1.PARMLIB.

You can specify the default for the ZIIP command option in your options module by using the ZIIP installation option (ZIIP=ENABLED). BMC AMI Copy ships with a default value of ENABLED for this option. The ZIIP option on the OPTIONS command overrides the default that is in the installation options module.

ZIIP values

Value

Description

ENABLED

BMC AMI Copy offloads eligible processing to an available zIIP. If the zIIP is busy or not available, normal processing continues on a general-purpose processor.

To enable and use zIIP processing with BMC AMI Copy, you must:

Have an installed authorized version of XBM or SUF
Start and maintain an XBM subsystem in your environment
Have a zIIP available in your environment

You can specify a particular XBM subsystem to use by specifying a value for the XBMID installation option (XBMID= ssid or xbmGroup) or XBMID option on the OPTIONS command ()**LINK** to XBMID ssid or xbmGROUP.

XBM and SUF are licensed, installed, and maintained separately from BMC AMI Copy. You can use either XBM or SUF, depending on the license that you have obtained:

A license for the full version of the XBM product authorizes you to use all features of XBM.
A license for SUF authorizes you to use only the snapshot and zIIP-processing features of XBM.

For more information about XBM and SUF, see the SNAPSHOT UPGRADE FEATURE for DB2 documentation.

DISABLED

BMC AMI Copy does not use zIIP processing.

OPTIONS syntax option description

On this page