Basic installation options description

• AUX=LOB—BMC AMI Copy includes only LOB objects with base space in the copy. You can include indexes for the auxiliary spaces by specifying INDEXES YES.
• AUX=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 can include the indexes by specifying INDEXES YES.
• AUX=ARCHIVE—Specifies if BMC AMI Copy should copy archive tables if table spaces with archive-enabled base tables are specified in SYSIN. It does not include related XML or LOB objects.

You can override the value of the AUX installation option at run time by using the AUX option on the OPTIONS command, the COPY command, the COPY IMAGECOPY command, or the EXPORT command. 

BINDQUALIFIER=ACP vvr

Use the BINDQUALIFIER installation option to specify the BMC AMI Copy bind qualifier for the dynamic bind process. The bind qualifier determines which set of synonyms BMC AMI Copy is to use. The BINDQUALIFIER value can have a maximum length 8 bytes. The default value is ACP vvr, where vv represents a two-character version number and r represents a one-character release number, such as ACP101. 

BMCSYSADM=adminuser

(BMC.DB2.SPE2410)

If the installation practice is to remove authority from the Install SYSADM, the installation can specify an alternate user ID for this access using the BMCSYSADM user options parameter. By default, the Install SYSADM user performs the dynamic bind process.

To use a different user other than the one specified in DB2 ZPARM, you can use BMCSYSADM user options parameter to assign a different user with SYSADM authority. This option does not give the user any additional Db2 authority and is specified only in the user options.

CHECKERR=4

The CHECKERR option specifies the default condition code to control the severity of page checking errors unless it is overridden at run time by the CHECKERROR syntax option. Valid values are 0 through 254. The default value is 4. A condition code higher than 4 causes the BMC AMI Copy execution to terminate at the point of error. A condition code of 4 or less allows execution to continue. For more information about CHECKERROR, see  Global-COPY-options.

For information about the availability of this option when you are copying the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA, see Copying-special-case-catalog-and-directory-table-spaces.

CHECKERR applies to both COPY and COPY IMAGECOPY executions.

CHECKLVL=0

The CHECKLVL option specifies the default level of page integrity checking used by BMC AMI Copy when the CHECKTSLEVEL option is not specified in a COPY command.

The default installation value is CHECKLVL=0 which specifies the same level of integrity checking as CHECKTSLEVEL 0. Similarly, if CHECKLVL=1 or CHECKLVL=2 is specified for installation and CHECKTSLEVEL is not specified in a COPY command, the level of integrity checking that corresponds to CHECKTSLEVEL 1 or CHECKTSLEVEL 2 respectively is used.

If CPU usage is more of a concern than integrity, set CHECKLVL to 0. When CHECKLVL=0 is specified during installation and CHECKTSLEVEL is not specified in the COPY or COPY IMAGECOPY command, standard minimal page integrity checking is performed by BMC AMI Copy. For more information about integrity checking, see Global-COPY-options and COPY-IMAGECOPY-syntax-options.

For information about the availability and handling of this option when you are copying the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, and DSNDB01.SYSDBDXA, see Copying-special-case-catalog-and-directory-table-spaces.

COMPRESS=NO

The COMPRESS option specifies if BMC AMI Copy is to compress disk image copies. The default value is COMPRESS=NO. Specify COMPRESS=YES to request compression using the BMC Extended Compression Architecture (XCA) technology. COMPRESS can be overridden at run time by the OPTIONS command COMPRESS option.

COPYDDN1=LP

The COPY DDN1 option specifies how to register the first data set named in the COPYDDN option (or SYSCOPY if it defaults) when multiple COPYDDN values are specified and RECOVERYDDN is not specified. In this situation, the first data set named by COPYDDN is registered based on the value of COPYDDN1, as follows:

• LP—local primary
• LB—local backup
• RP—recovery primary
• RB—recovery backup

The value used for COPYDDN1 cannot be reused for COPYDDN2, COPYDDN3, or COPYDDN4.

If only one value is specified for COPYDDN and RECOVERYDDN is not specified, the data set is registered as a local primary copy. Also, if RECOVERYDDN is specified, the data set is registered as a local primary copy.

This option is ignored when you are copying the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA. 

COPYDDN2=LB

The COPY DDN2 option specifies how to register the second data set identified in the COPYDDN option when multiple values are specified for COPYDDN and RECOVERYDDN is not specified. When multiple values are specified for COPYDDN and RECOVERYDDN is not specified, the second data set identified by COPYDDN is registered based on the value of COPYDDN2, as follows:

• LP—local primary
• LB—local backup
• RP—recovery primary
• RB—recovery backup

The value used for COPYDDN2 cannot be reused for COPYDDN1, COPYDDN3, or COPYDDN4.

If RECOVERYDDN is specified, the second data set specified by COPYDDN is registered as a local backup copy.

This option is ignored when you are copying the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA.

COPYDDN3=RP

The COPY DDN2 option specifies how to register the third data set identified in the COPYDDN option when multiple values are specified for COPYDDN and RECOVERYDDN is not specified. When multiple values are specified for COPYDDN and RECOVERYDDN is not specified, the third data set identified by COPYDDN is registered based on the value of COPYDDN3, as follows:

• LP—local primary
• LB—local backup
• RP—recovery primary
• RB—recovery backup

The value used for COPYDDN3 cannot be reused for COPYDDN1, COPYDDN2, or COPYDDN4.

If RECOVERYDDN is specified, the third data set specified by COPYDDN is invalid and is ignored.

This option is ignored when you are copying the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA.

COPYDDN4=RB

The COPY DDN4 option specifies how to register the fourth data set identified in the COPYDDN option when multiple values are specified for COPYDDN and RECOVERYDDN is not specified. When multiple values are specified for COPYDDN and RECOVERYDDN is not specified, the fourth data set identified by COPYDDN is registered based on the value of COPYDDN4, as follows:

• LP—local primary
• LB—local backup
• RP—recovery primary
• RB—recovery backup

The value used for COPYDDN4 cannot be reused for COPYDDN1, COPYDDN2, or COPYDDN3.

If RECOVERYDDN is specified, the fourth data set specified by COPYDDN is invalid and is ignored.

This option is ignored when you copy the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA.  

DATAMVR=

The DATAMVR installation 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.

You can override the value of the DATAMVR installation option at run time by using the DATAMVR option on the OPTIONS command. 

DB2NTRY=10

The DB2NTRY option specifies the maximum number of times to attempt to use a resource before concluding that the resource cannot be obtained. You can use any integral value from 1 through 255 for DB2NTRY. The default is 10. DB2NTRY can be overridden at run time by the OPTIONS command DB2NTRY option. See the preceding description of DB2WAIT.

For information about the availability and handling of this option when you are copying the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA, see Copying-special-case-catalog-and-directory-table-spaces.

DB2NTRY applies to both COPY and COPY IMAGECOPY executions. 

DB2WAIT=3

The DB2WAIT option specifies the time 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.

You can use any integer value from 1 through 655 for DB2WAIT. The default is 3 seconds. Note that the waiting time specified by DB2WAIT is additional to Db2 resource timeout and utility values IRLMRWT and UTIMOUT set in DSNZPARM. DB2WAIT can be overridden at run time by the OPTIONS command DB2WAIT option.

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 the result of the formulas above.

For information about the availability and handling of this option when you are copying the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA, see Copying-special-case-catalog-and-directory-table-spaces.

DB2WAIT applies to both COPY and COPY IMAGECOPY executions.  

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. 

DISPLOCK=NO

When using SHRLEVEL CHANGE and data sharing, the DISPLOCK option determines the use of DISPLAY LOCKS in group buffer pool dependence. The default value is DISPLOCK=NO. DISPLOCK=NO avoids issuing DISPLAY LOCKS and uses a different internal technique to determine the group buffer pool dependency. DISPLOCK=YES indicates the use of DISPLAY LOCKS. DISPLOCK=ONLY tells BMC AMI Copy to use DISPLAY LOCKS ONLY to display table spaces and tables that have locks.

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.

DRNWAIT

(BMC.DB2.SPE2310)

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.

You must reassemble the installation options module when you specify a new value for DRNWAIT. If you do not reassemble the module, the default value 20, is used. 

You can override DRNWAIT at run time by using the DRAINWAIT option from the OPTIONS command. For more information, see DRAINWAIT in OPTIONS-syntax-option-description.

DRNRETRY

(BMC.DB2.SPE2310)

Specifies the maximum number of retries to attempt. The valid value ranges from 0 through 999. The default value is 100.

You must reassemble the installation options module when you specify a new value for DRNRETRY. If you do not reassemble the module, the default value 100, is used. 

You can override DRNRETRY at run time by using the DRAINRETRY option from the OPTIONS command. For more information, see DRAINRETRY in OPTIONS-syntax-option-description.

DRNDELAY

(BMC.DB2.SPE2310)

Specifies the minimum duration, in seconds, between retries. The valid value ranges from 1 through 1800. The default value is 100.

You must reassemble the installation options module when you specify a new value for DRAINDELAY. If you do not reassemble the module, the default value 100, is used. 

You can override DRNDELAY at run time by using the DRAINDELAY option from the OPTIONS command. For more information, see DRAINDELAY in OPTIONS-syntax-option-description.

ERRSKIP=YES

The ERRSKIP installation option specifies the default value for the ON ERROR INTEGRITY global Copy option.

The following values are valid for the ERRSKIP installation option:

• YES—(Default)  BMC AMI Copy defaults to ON ERROR INTEGRITY SKIP. If a space has been corrupted (for example, the page number is incorrect), BMC AMI Copy issues an error message, skips the corrupted space, and the job step continues to copy any other spaces that were specified.
• NO—BMC AMI Copy defaults to ON ERROR INTEGRITY END. If space is corrupted, BMC AMI Copy issues an error message and the job step terminates.

For more information, see ON-ERROR-INTEGRITY.

ESCALATE=YES

The ESCALATE option specifies if BMC AMI Copy is to allow automatic escalation of FULL NO copies to FULL YES copies when any of the following conditions occur:

• An incremental copy is prohibited by an entry in SYSIBM.SYSCOPY
• The target table space or partition is in COPY-pending status
• The target space is a special case catalog or directory space (DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA)

Automatic escalation is not allowed for the listed conditions when ESCALATE is set to NO. For more information, see Escalating-incremental-copies-to-full-copies.

FCPPRC=NONE

The FCPPRC installation option controls what happens if you specify SNAP=VSAM and the data sets are on a disk that is capable of FlashCopy.

The following values are valid for the FCPPRC installation option when the target volume is a primary in a PPRC mirror pair:

• PREF specifies that preserving the mirror during the FlashCopy is preferred.
• REQ specifies that preserving the mirror is required.
• NO specifies that the mirror is not to be preserved during a FlashCopy.
• NONE, the default, specifies that no FCTOPPRCPRIMARY option is passed to DFDSS. 

FULLPCT=50

The FULLPCT option specifies if BMC AMI Copy is to escalate a FULL AUTO or CHANGELIMIT incremental copy request to a full copy request if the number of changed pages is equal to or greater than the value specified (based on the modification indicators in the space map page). Valid values are integers from 0 through 100. The default value is 50% and can be overridden at run-time by specifying the FULLPCT or CHANGELIMIT syntax option (which allows the specification to the hundredth place).

For more information about the FULLPCT and CHANGELIMIT syntax options, see Global-COPY-options. 

FULLRESET=NO

Use the FULLRESET installation option to change SHRLEVEL CHANGE RESETMOD NO copies to use RESETMOD YES if BMC AMI Copy makes full copies when you specify FULL AUTO or CHANGELIMIT. Valid values are NO and YES. The default value is NO.

If you specify FULLRESET=YES and SLCHGRESET is NO, BMC AMI Copy invokes DSNUTILB to make the full copy with RESETMOD YES. If SLCHGRESET is YES, BMC AMI Copy will make a copy natively with 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.

You can override the value of the FULLRESET installation option at run time by using the FULLRESET option on the OPTIONS command or on the COPY command.

GENSYSPAGES=NO

The GENSYSPAGES installation option specifies whether to verify that a system page exists for the latest ALTER. If you are creating a copy for migration and the copy does not contain a system page for the latest version, REPAIR VERSIONS on the target might not work correctly. BMC AMI Copy can automatically generate the system page before making the copy.

The following values are valid for the GENSYSPAGES installation option:

• NO—(Default) Tells BMC AMI Copy not to check for a system page for the latest ALTER.
• AUTO—Tells BMC AMI Copy to check for a system page for the latest ALTER and, if the page does not exist, to generate it.

BMC AMI Copyuses the BMCXCOPY table to track the current version of the system pages. When BMC AMI Copy checks for system pages or generates system pages, BMC AMI Copy inserts a row into BMCXCOPY with ICTYPE s even if the copy is registered in SYSCOPY.

You can use GENSYSPAGES with SHRLEVEL CHANGE, SHRLEVEL REFERENCE, or SHRLEVEL CONCURRENT copies.

You can override the value of the GENSYSPAGES installation option at run time by specifying the GENSYSPAGES option on the COPY command.

HISTORY=NO

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. Valid values for this option are

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

For the contents of the BMCHIST table, see Common-utility-tables.

You can override HISTORY at run time by specifying the HISTORY option on the OPTIONS command. For more information, see HISTORY in OPTIONS-syntax-option-description.

HISTRETN=0

The HISTRETN option specifies the number of days to keep entries in the BMC history table (BMCHIST). BMC AMI Copy deletes entries older than the number of days specified. Valid values for HISTRETN are 0 to 999. The default is HISTRETN=0, which specifies that BMC AMI Copy is not to delete any rows. Deletions are based on the DBNAME, SPNAME, UTILNAME, and DATE columns in the history table.

HISTRETN operates independently of the HISTORY=YES or NO installation option.

HISTRETN can be overridden at run time with the OPTIONS command HISTRETN option. For more information, see HISTRETN in OPTIONS-syntax-option-description. 

ICAUTOF=A

The ICAUTOF option specifies the value to use for the &ICTYPE symbolic variable when FULL AUTO or CHANGELIMIT produces a full copy. The default is A. The alternative value is F. You can use this symbolic variable on the OUTPUT statement to create easily identifiable full copy data set names. For more information about symbolic variables, see Using-symbolic-variables.

ICAUTOI=A

The ICAUTOI option specifies the value to use for the &ICTYPE symbolic variable when FULL AUTO or CHANGELIMIT produces an incremental copy. The default is A. The alternative value is I. You can use this symbolic variable on the OUTPUT statement to create easily identifiable incremental copy data set names. For more information about symbolic variables, see Using-symbolic-variables. 

INCRPCT=0

The INCRPCT option specifies that BMC AMI Copy is to take an incremental image copy if the percent of changed pages is greater than the value specified for INCRPCT but less than the value of FULLPCT (based on the modification indicators in the space map page). Valid values are integers from 0 through 100. The default value is 0% and can be overridden at run-time by specifying the FULLPCT or CHANGELIMIT syntax option (which allows the specification to the hundredth place). No image copy is taken if the percent of changed pages is equal to or less than the value specified for INCRPCT (unless you specify EMPTY NO and BMC AMI Copy can acquire a registration point).

For more information about the FULLPCT and CHANGELIMIT syntax options, see Global-COPY-options. 

INVCACHE=NO

The INVCACHE option allows you to specify whether BMC AMI Copy invalidates the dynamic SQL statement cache with RUNSTATS. Valid values are YES and NO. The default is INVCACHE=NO, which does not invalidate the cache. INVCACHE =YES 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 the latest access path changes are picked up.

INVCACHE can be overridden at run time by specifying the INVCACHE option on the OPTIONS command. Also, see Statistics-collection. 

IXDSNUM=ALL

The IXDSNUM option sets the default for DSNUM for indexes, and thus, determines how indexes are copied. Valid values are DATASET and ALL with ALL being the default. Index copies are specified via COPY TABLESPACE, INDEXES YES or COPY INDEXSPACE. If DSNUM is not specified, DSNUM for index spaces is set to the value of IXDSNUM. If DSNUM is specified, the DSNUM specification works with the value of IXDSNUM to determine how indexes are copied. The IXDSNUM installation option can be overridden at run time by the IXDSNUM option on the OPTIONS command.

IXEXPAND = AUTO

The IXEXPAND option specifies how BMC AMI Copy handles compressed indexes. IXEXPAND=AUTO is the default value. When IXEXPAND=AUTO, BMC AMI Copy determines if you are running with a Recovery Management for Db2 password. If you are using Recovery Management for Db2, BMC AMI Copy uses IXEXPAND=NO and makes image copies of compressed indexes that are registered in BMCXCOPY and used by the BMC AMI Recover product. If you are not running with a Recovery Management for Db2 password, BMC AMI Copy uses IXEXPAND=YES and expands the compressed indexes before making image copies that are registered in SYSCOPY and are compatible with the IBM Db2 COPY utility.

If you are performing a Db2 catalog copy and you are running under a Recovery Management for Db2 password, you should set IXEXPAND=YES to prevent an error caused by IXEXPAND=AUTO (the default value) converting to IXEXPAND=NO.

When BMC AMI Copy uses IXEXPAND=YES, some BMC copy techniques, such as Instant Snapshots and online consistent copies, are not supported.

You can override the IXEXPAND installation option value at run time by specifying the IXEXPAND option on the OPTIONS command.

For more information about support for compressed indexes, see Copying-compressed-indexes. 

IXSIZE=0

The IXSIZE option specifies a size threshold for making index copies using COPY INDEX and COPY INDEXSPACE, and COPY TABLESPACE INDEXES YES. Unless this threshold is met or exceeded, no index copy is made. The default is 0, which means that all indexes are copied.

You can specify IXSIZE as a number of pages. Valid values for number of pages are 0 to 1,073,741,823.

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

• IXSIZE= integer with a limit of 4,294,967,295 kilobytes
• IXSIZE= integer with a limit of 4,194,303 megabytes
• IXSIZE= integer with a limit of 4095 gigabytes

The IXSIZE installation option can be overridden at run time by the IXSIZE option on the OPTIONS command.

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

IXSIZET=M

The IXSIZET option specifies the units used for the IXSIZE installation option. The default value for IXSIZET is M for megabytes. Valid values are:

• K for kilobytes (with a limit of 4,294,967,295)
• M for megabytes (limit of 4,194,303)
• G for gigabytes (limit of 4095)

If none of the above is specified, BMC AMI Copy assumes that the integer specified by IXSIZE is for the number of pages (with a limit of 1,073,741,823).

KEYDSNAM= keyDataSetName

The KEYDSNAM option specifies the name of the key data set that is used for encrypted copies.

For more information about encrypted copies and the key data set, see Making-encrypted-copies. 

MAXINCRS=6

The MAXINCRS option specifies that BMC AMI Copy is to escalate a FULL AUTO or CHANGELIMIT incremental copy request to a full copy request if 6 non-merged (CUMULATIVE NO) incremental copies have already been made since the last full copy. Valid values are in the range 1 through 100. The default value can be overridden at run-time by specifying the MAXINCRS syntax option. For more information about the MAXINCRS syntax option, see Global-COPY-options. 

MAXTASKS=(1,AUTO)

The MAXTASKS installation option specifies the number of subtasks for tape output and the maximum number of subtasks to use when making copies. Sub-tasking applies to all COPY TABLESPACE, COPY INDEXSPACE, COPY INDEX, or COPY IMAGECOPY commands. You can override this installation option at run time by using the MAXTASKS syntax option on the OPTIONS command. For more information, see Using-Multitasking.

The MAXTASKS syntax is MAXTASKS=(tapeTasks[, totalTasks]). The tapeTasks value is required. The brackets ([ ]) indicate that the totalTasks value is optional. 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 tape 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 want BMC AMI Copy to perform no subtasking, specify MAXTASKS (1,1), and BMC AMI Copy will do all work in the main task.

If you specify multitasking, each task requires a DD with the naming convention ACPPRTnn where nn is the task number, 01 through 32. If you do not code a DD statement, BMC AMI Copy dynamically allocate ACPPRTnn to system output (SYSOUT). If SYSOUT is not used and DISP=OLD, BMC AMI Copy opens it OLD from the main task to clear it initially. Then BMC AMI Copy opens it DISP=MOD in the subtasks so that it will not be overlaid by each subsequent invocation of the task. This process is similar to the current handling of SYSPRINT.

MIGRVOL=

The MIGRVOL option specifies an additional volume to be considered migrated or archived when MIGRSKIP=YES is specified. The MIGRVOL installation option can be overridden at run time by the MIGRVOL option on the OPTIONS command. 

MIGRSKIP=NO

The MIGRSKIP option specifies whether to skip migrated or archived spaces. The default is NO. Specify YES to have BMC AMI Copy skip migrated or archived spaces. Volumes MIGRAT and ARCIVE, as well as any volume specified with the MIGRVOL option, are skipped if MIGRSKIP=YES is specified. MIGRSKIP YES does not apply to spaces having more than one part and DSNUM ALL. The MIGRSKIP installation option can be overridden at run time by the MIGRSKIP option on the OPTIONS command. 

MINPAGES=180

The MINPAGES option specifies that BMC AMI Copy is to escalate a FULL AUTO or CHANGELIMIT incremental copy request to a full copy request if less than the number of pages specified for MINPAGES exists in space or partition. The default value is 180. The default value can be overridden at run-time by specifying the MINPAGES syntax option. For more information about the MINPAGES syntax option, see Global-COPY-options. 

NBRBUFS=4

The NBRBUFS option specifies how many read/write buffers to use and manage. Valid values for NBRBUFS are 2 through 16. NBRBUFS applies to both COPY and COPY IMAGECOPY executions. NBRBUFS can be overridden at run time by the OPTIONS command NBRBUFS option.

More buffers allow more read and write-ahead capability. However, more buffers require more memory (up to 737280 bytes per buffer) and, because more buffer management is required, more 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.

OPNDB2ID=YES​​​​​​

(BMC.DB2.SPE2504)

The OPNDB2ID option specifies whether to use the Db2 RACF ID instead of your RACF ID running BMC AMI Copy when opening Db2 data sets and Boot strap datasets.

Specifying OPNDB2ID=NO tells BMC AMI Copy to use your RACF ID running BMC AMI Copy. If NO is specified, you must have RACF authority for the Db2 data sets being copied.

If your Db2 is specified in the RACF started procedures table (ICHRIN03) as a privileged or trusted task and no user ID is associated with the Db2 address space, you cannot use OPNDB2ID to allow BMC AMI Copy to access the Db2 data sets. In this case, you are running BMC AMI Copy then you must have RACF authority to access the data sets needed for recovery.

For any security system other than RACF, OPNDB2ID should be set to NO. 

OUTSIZE=0

The OUTSIZE option 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 default is 0, which means this option has no effect.

OUTSIZE can be specified as the number of pages. Valid values for number of pages are 0 to 1,073,741,823.

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

• OUTSIZE= integer with a limit of 4,294,967,295 kilobytes
• OUTSIZE= integer with a limit of 4,194,303 megabytes
• OUTSIZE= integer with a limit of 4095 gigabytes

If the value is greater than 0 and 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, the image copy output will go to an alternate set of DDs that are specified with the following keywords (described in COPY-object-options):

• BIGDDN
• BIGDSN
• BIGRECDDN
• BIGRECDSN

OUTSIZE requires the use of dynamic allocation and can be used with any FULL option. The size of the copy is based on the size of a full copy. Also, see Allocating-output-copy-data-sets-dynamically.

The OUTSIZE installation option can be overridden at run time by the OUTSIZE option on the OPTIONS command. 

OUTSIZT=P

The OUTSIZT option specifies the units used for the OUTSIZE installation option. By default, OUTSIZT assumes the integer specified by OUTSIZE is for the number of pages (with a limit of 1,073,741,823). Other valid values are:

• K for kilobytes (with a limit of 4,294,967,295)
• M for megabytes (with a limit of 4,194,303)
• G for gigabytes (with a limit of 4095) 

PLANCOPY=ACPBvvr

The PLANCOPY option specifies the execution plan for the current release of BMC AMI Copy.

The execution plan handles the following functions:

• Verifies that the table space you specified exists and that you have sufficient Db2 authorization to run BMC AMI Copy.
• Performs catalog lookup for information about the table space to be copied.
• Checks to see if the table space is already in use by a Db2 utility or another BMC utility job.
• Inserts rows into SYSIBM.SYSCOPY if you specify the FULL YES or FULL NO option.

PLANCOPY applies to both COPY and COPY IMAGECOPY executions. The default value is ACPB vvr, where vv represents a two-character version number and r represents a one-character release number, such as ACPB101. 

PUBLICPLAN=YES

Use the PUBLICPLAN installation option to grant the PUBLIC privilege to run BMC AMI Copy. Valid values for PUBLICPLAN are YES and NO. The default value is YES. Specify PUBLICPLAN=YES if you want BMC AMI Copy to grant the execute privilege to PUBLIC whenever the BMC AMI Copy plan is dynamically bound. If you set the value of this option to NO, BMC AMI Copy will not do any grants, which means that you must grant execute authority to users as needed. 

QSCBEF=NO

The QSCBEF option specifies whether BMC AMI Copy is to set QUIESCE BEFORE for a COPY TABLESPACE or COPY INDEXSPACE command. Valid values are NO and YES. The default is NO. 

READONLY=STARTRO

The READONLY option specifies whether BMC AMI Copy should always set the space status to RO while initializing the connection to XBM in preparation for making SHRLEVEL CONCURRENT copies. Specify READONLY=LOCKTBL to tell BMC AMI Copy to use LOCK TABLE during the initialization.

Specify READONLY=DRAIN to tell BMC AMI Copy to use DRAIN during the initialization.

READONLY=STARTRO and READONLY=DRAIN allow operation at the partition level. READONLY=LOCKTBL does not allow operation at the partition level and results in the entire table space being locked. For more information, see Making-SHRLEVEL-CONCURRENT-copies-Snapshot-Copies.

You can override the READONLY value at run time by using the OPTIONS command READONLY option. 

READPCT=10

The READPCT option specifies that BMC AMI Copy is to escalate an incremental copy request from random read to full table space scan if the number of changed pages exceeds 10% (based on the modification indicators in the space map page). Valid values are in the range 1 through 100. You can override the default value of 10 at run-time by specifying the READPCT syntax option in conjunction with READTYPE AUTO. For more information about the READPCT syntax option, see Global-COPY-options.

REGISTEROCC=BMCXCOPY

Use this option to register online consistent copy (OCC) as 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. Valid values are BMCXCOPY and SYSCOPY. The default is BMCXCOPY. If you specify LP for SYSCOPY, an LP OCC  is registered in SYSCOPY and can be used directly by IBM RECOVER.  

REGWTO=NO

For copies written to disk, the REGWTO option allows you to specify whether BMC AMI Copy issues a WTO after the copy is successfully registered in SYSCOPY (after COMMIT) and after the data set has been unallocated. Valid values are YES and NO. The default is REGWTO=NO, which does not issue the WTO. 

RESETCHG=YES

The RESETCHG option specifies whether BMC AMI Copy, when it is the last utility to relinquish control of a space while doing a SHRLEVEL CHANGE copy, is to put the space back in its initial status or not. Specifying RESETCHG=YES, the default, directs BMC AMI Copy to place the space in its initial status. If RESETCHG=NO is specified, BMC AMI Copy will not change the status of a space to its initial status. 

RESETMOD=NO

The RESETMOD option specifies that BMC AMI Copy is not to reset the modified-page indicators in the table space. Specifying RESETMOD=YES tells BMC AMI Copy to reset the indicators. The default value can be overridden at run-time by specifying the RESETMOD syntax option. For more information about the RESETMOD syntax option, see RESETMOD. For information about status changes, see Db2-commands-issued-by-BMC-AMI-Copy-for-read-and-write-databases.

SLCHGQSC=YES

When BMC AMI Copy is unable to acquire a valid RBA or LRSN to register a SHRLEVEL CHANGE copy, the SLCHGQSC option determines what action BMC AMI Copy takes. The default value SLCHGQSC=YES directs BMC AMI Copy to invoke the QUIESCE utility when BMC AMI Copy is unable to acquire a valid RBA or LRSN for registration. If SLCHGQSC=NO and BMC AMI Copy is unable to acquire a valid RBA or LRSN for registration, the step ends with an error message, unless the copy is an incremental copy. For an incremental copy, if the STARTRBA for the copy is not greater than the STARTRBA of the prior copy and SLCHGQSC=NO, BMC AMI Copy bypasses the incremental copy because it would not result in a reduction of log apply during recovery. 

If SLCHGQSC=YES and SOFTQUIESCE=YES, it performs the DRAIN function instead of a QUIESCE. Also, DRAINWAIT, DRAINDELAY, and DRAINRETRY apply in this case. 

SLCHGRESET

The SLCHGRESET installation option specifies how to process SHRLEVEL CHANGE RESETMOD YES copies.

The following values are valid for the SLCHGRESET installation option:

• YES BMC AMI Copy makes native SHRLEVEL CHANGE RESETMOD YES copies.
• NO BMC AMI Copy invokes DSNUTILB for SHRLEVEL CHANGE RESETMOD YES copies.

This value can be overridden at run time by using the SLCHGRESET option on the OPTIONS command. 

SNAP=HW

The SNAP installation 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.

The following values are valid for the SNAP installation option:

• HW (Default)
  When SNAP=HW, BMC AMI Copy calls XBM to make an Instant Snapshot 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

  When SNAP=VSAM, BMC AMI Copy calls DFSMSdss to copy a VSAM data set using conventional I/O if the source or target is not on a snappable disk. If the data sets are on 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, BMC AMI Copy uses FAST REPLICATION REQUIRED. You can use the following example syntax when you specify SNAP=VSAM:

  OUTPUT LOCALP
     DSSNAP YES                                    
     DSNAME dataSetName
  
  COPY  TABLESPACE tableSpaceName
     DSNUM DATASET

  SNAP=VSAM is supported only when the target data set is SMS-managed. If the target data set is not SMS-managed, the copy fails.

You can override the value of the SNAP installation option at runtime by using the SNAP option in the OPTIONS command. 

SQUEEZE=NO

The SQUEEZE option, by default, specifies that BMC AMI Copy is not to consolidate the rows on a table space page and make all of the free space contiguous unless this option value is overridden at run time by the SQUEEZE syntax option. Specify SQUEEZE=YES to request consolidation. For more information, see SQUEEZE.

For information about the availability of this option when you are copying the Db2 catalog and directory table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, or DSNDB01.SYSDBDXA, see Copying-special-case-catalog-and-directory-table-spaces.

SQUEEZE applies to both COPY and COPY IMAGECOPY executions.

SMARTSTK=YES

The SMARTSTK option allows you to specify whether or not BMC AMI Copy stacks incremental copies in the same logical stacking order as their associated full copies. The default value is YES. Specifying SMARTSTK=YES tells BMC AMI Copy to analyze the stacking order for the associated full copies and stack the incremental copies in the same order. SMARTSTK=YES requires the use of grouping. Specifying SMARTSTK=NO tells BMC AMI Copy that no stacking analysis for incremental copies will be done. They will be stacked as they are processed. The SMARTSTK installation option can be overridden at run time by the SMARTSTACK option on the OPTIONS command or the COPY command. 

STOPCMT=NO

The STOPCMT option specifies whether to add the AT(COMMIT) parameter to all DB2 STOP commands that BMC AMI Copy issues. STOPCMT=YES adds the AT(COMMIT) parameter. STOPCMT=NO, the default, does not. See the IBM DB2 for z/OS Command Reference for details and implications of the AT(COMMIT) parameter. For information about when BMC AMI Copy issues a DB2 STOP command, see Db2-commands-issued-by-BMC-AMI-Copy-for-read-and-write-databases.

SYSBACKUP=NO

The SYSBACKUP installation option specifies whether image copies derived from system-level backups will be considered by COPY IMAGE COPY.

The following values are valid for the SYSBACKUP installation option:

• YESCOPY IMAGECOPY command includes image copies derived from system-level backups in the set of candidate image copies.
• (Default) NOCOPY IMAGECOPY command ignores image copies derived from system-level backups in the set of candidate image copies.

This value can be overridden at run time by using the SYSBACKUP option on the OPTIONS command. 

SYSUDUMP=YES

The SYSUDUMP option indicates if BMC AMI Copy is to dynamically allocate SYSUDUMP. The default value is SYSUDUMP=YES. You can also specify SYSUDUMP=Y. If you specify SYSUDUMP=YES or SYSUDUMP=Y and a SYSUDUMP DD statement is not specified in the BMC AMI Copy step, BMC AMI Copy dynamically allocates SYSUDUMP using the default output class. Specify NO or N to not have SYSUDUMP allocated.

BMC AMI Copyautomatically takes an SVCDUMP when it abends. 

UPDATECLRSN=YES

The UPDATECLRSN option updates the CLRSN. The CLRSN must be updated to reset COPYUPDATEDPAGES.

The following values are valid for the SLCHGRESET installation option:

• 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

USELARGEBLK=YES

Use the USELARGEBLK installation option to control the creation of image copies with BLKSIZE greater than 32760. Valid values for USELARGEBLK are YES and NO. The default value is YES. With USELARGEBLK=YES, BMC AMI Copy creates image copies with block sizes greater than 32760. With USELARGEBLK=NO, BMC AMI Copy will not create image copies with block sizes greater than 32760. 

UTRETRY=NO

The UTRETRY option allows you to specify that BMC AMI Copy retry using normal retry parameters if a UTxx status is found and the space is in use by another Db2 utility (message BMC30121E SPACEdatabaseName.spaceName ALREADY IN USE BY A Db2 UTILITY). If the UT xx condition clears, then BMC AMI Copyproceeds. If the retry is exhausted, an error occurs. Valid values are YES and NO. The default is UTRETRY=NO, which does not retry.

WKUNIT=SYSALLDA

The WKUNIT option specifies the unit for work data sets dynamically allocated by BMC AMI Copy. If you do not want to use SYSALLDA, you can change to some other appropriate generic name. Do not specify VIO for this option. 

WORKPREFIX

The WORKPREFIX installation option provides BMC AMI Copy with a high-level qualifier to use in creating temporary data sets. The default value is your TSO ID submitting the copy job. This value can be overridden by using the WORKPREFIX option on the OPTIONS command.

XBMID= ssid or xbmGroup

The XBMID option specifies the XBM or SUF ssid (subsystem ID) 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.

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.

Use of XBMID with SHRLEVEL CONCURRENT is described in the OPTIONS command XBMID option.

You can override the value for this option by using the OPTIONS command XBMID option. 

XBMMNTR=NO

The XMBMNTR option indicates if you want to use the Utility Monitor available with the BMC EXTENDED BUFFER MANAGER (XBM) or SNAPSHOT UPGRADE FEATURE (SUF) products to view the status of your copies. The default is NO indicating that you are not going to use the Utility Monitor. Specify YES to use the Utility Monitor.  For more information, see the SNAPSHOT UPGRADE FEATURE for DB2 documentation.

XBMMNTR can be overridden at run time by specifying the OPTIONS command XBMMNTR option. 

XBMRSTRT=NO

The XBMRSTRT option indicates whether copies made with SHRLEVEL CONCURRENT specified are restartable in the COPY phase. The default is XBMRSTRT=NO. For Snapshot Copies, XBMRSTRT=YES requires more cache but allows BMC AMI Copy to continue on restart where it left off instead of restarting in the UTILINIT phase. XBMRSTRT can be overridden at run time by the OPTIONS command XBMRSTRT option.  

XCFGROUP=$ACPXCF

The XCFGROUP option specifies the XCF group name used by BMC AMI Copy for cross system communication when making SHRLEVEL CHANGE copies in a data sharing environment.

The default is $ACPXCF. Valid values are valid XCF group names. The XCF group name must meet IBM’s requirements, as follows:

• The name must be 1 to 8 characters long.
• The valid characters for use in the name are A-Z, 0-9, and national characters ($, #, and @).

To avoid using the names IBM uses for its XCF groups, do not begin group names with the letters A through I or the character string SYS. Also, do not use the name UNDESIG, which is reserved for use by the system programmer at your installation. Do not use a name used by any other software product. 

XCFWAIT=10

The XCFWAIT option specifies the number of minutes the main copy job will wait for an agent to join the group or for a response to a request to an agent.

Valid values are 0 through 255 minutes. The default is 10 minutes and is performed three times for a total of 30 minutes. If 0 is specified, there is no limit on the wait. 

ZIIP=ENABLED

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

You can specify one of the following values:

• ENABLED—Tells BMC AMI Copy to attempt to offload eligible processing to an available zIIP. If the zIIP is busy or not available, normal processing continues on a general-purpose processor.
• DISABLED—Tells BMC AMI Copy to not attempt to use zIIP processing.

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 or OPTIONS command XBMID option.

XBMand 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

You can override the value for this option by using the ZIIP command option.