The FULL option lets you specify full image copies or incremental image copies of the table space or data set you want to copy. Use FULL YES (the default) for full image copies, FULL NO for incremental copies, or FULL AUTO to tell
BMC AMI Copy
when to escalate an incremental image copy request to a full image copy request.
The following rules apply when you use FULL AUTO:
- If you specify only FULL AUTO, BMC AMI Copy defaults to FULL AUTO FULLPCT (0, fullPct) where fullPct is taken from your current installation options module.
- If you specify FULL AUTO with CUMULATIVE YES and either SHRLEVEL NONE or SHRLEVEL REFERENCE, and the request escalates to FULL YES, BMC AMI Copy automatically uses RESETMOD YES.
- If an incremental image copy is produced as a result of using FULL AUTO, CHECKTSLEVEL 2 is automatically adjusted to CHECKTSLEVEL 1.
- FULL AUTO is allowed with table spaces with the TRACKMOD NO attribute, but only with MAXINCRS and FULLDAY for determining whether to make full or incremental copies.
All the options you can specify with FULL NO are available with FULL AUTO.
Important
When copying the following Db2 catalog and directory table spaces you should make only full image copies:
- DSNDB06.SYSCOPY
- DSNDB01.SYSUTILX
- DSNDB01.DBD01
- DSNDB01.SYSDBDXA
Copying-the-Db2-catalog-and-directory provides more information.
FULL syntax diagram
FULL YES
FULL YES is the default and lets you create up to four full image copies of the target space, index, partition, or data set. If you also specified DSNUM integer then, for a partitioned space, the copies are for the specified partition; for a nonpartitioned space, the copies are for the specified data set.
| |
|---|
| You can now use migration-only copies to migrate data to another system. Because these copies are registered differently than normal copies, they do not interfere with the image copies used for recovery. Use the HIDDEN option to create hidden full copies. These copies are not used for recovery. They are also not used as the basis of an incremental copy. |
|---|
FULL NO
If you use FULL NO, BMC AMI Copy creates up to four incremental image copies of the space, partition, or data set. If you also specify DSNUM integer then, for a partitioned space, the copies are for the specified partition; for a nonpartitioned space, the copies are for the specified data set.
If you use FULL NO (or FULL AUTO or CHANGELIMIT) and specify CUMULATIVE YES and an incremental copy of the same type is already registered in SYSIBM.SYSCOPY with the RESETMOD NO option, BMC AMI Copy merges the new incremental copy and the existing incremental copy. If you specify KEEP NO, BMC AMI Copy deletes the entry for the existing incremental copy from SYSIBM.SYSCOPY; otherwise, the entry is retained.
The following conditions apply when you use FULL NO:
BMC AMI Copy automatically escalates a FULL NO request to a FULL YES request when any of the following conditions occur and the installation option ESCALATE is set to YES:
- An entry in SYSIBM.SYSCOPY prohibits an incremental copy.
- The target space or partition is in COPY-pending status.
- You are copying special case table spaces.
If ESCALATE is set to NO, escalation is not allowed. Escalating-incremental-copies-to-full-copies and Copying-special-case-catalog-and-directory-table-spaces provide more information.
- You cannot use CHECKTSLEVEL 2 when you specify FULL NO.
- If you specify SHRLEVEL CONCURRENT with FULL NO, BMC AMI Copy analyzes open log ranges to determine if any changes have been made since the last copy. If no changes were made since the last copy, no pages would be copied, so the copy for the space is skipped.
FULL AUTO
Use the FULL AUTO option when you want BMC AMI Copy to determine whether to make no copy, an incremental copy, or a full copy. When you specify FULL AUTO with MAXINCRS, BMC AMI Copy escalates an incremental copy request to a full copy request when the specified number of incremental copies has been reached.
FULL AUTO syntax diagram
| |
|---|
FULLPCT | The FULLPCT option specifies the boundaries for producing an incremental, full, or no copy based on the percentage of changed pages in the space, partition, or data set. Important Specifying FULL AUTO FULLPCT is the same as using CHANGELIMIT (CHANGELIMIT). The FULL AUTO FULLPCT option and the CHANGELIMIT option are effectively the same and act on two values - incrPct and fullPct to determine what type of copy to make. incrPct and fullPct are positional parameters. If a comma is used in the expression and incrPct is not specified, it defaults to installation option INCRPCT. If a comma is used and fullPct is not specified, it defaults to installation option FULLPCT. incrPct Specifies a percent of changed pages used to determine whether to make an incremental copy or no copy. incrPct is optional. incrPct must be an integer or decimal value from 0 to 100. A decimal value can be specified to the hundredth’s place (1/100 of a percent). The decimal point is not required when specifying a whole integer. fullPct Specifies a percent of changed pages used to determine whether to make a full copy instead of an incremental copy. fullPct is required. fullPct must be an integer or decimal value from 0 to 100. A decimal value can be specified to the hundredth’s place (1/100 of a percent). The decimal point is not required when specifying a whole integer. FULL AUTO FULLPCT(incrPct, fullPct) or CHANGELIMIT(incrPct,fullPct) are evaluated as follows: - If percent changed pages is less than or equal to incrPct, (x <= incrPct), do not make a copy.
- If percent changed pages is greater than incrpct but less than fullPct, (incrPct < x < fullPct), make an incremental copy.
- If percent changed pages is greater than or equal to fullPct, (x >= fullPct), make a full copy.
To bypass a copy for a space with no changed pages, specify FULL AUTO or CHANGELIMIT(0,fullPct). In this case, BMC AMI Copy makes an incremental copy if any pages have changed or a full copy if the percentage of changed pages equals or exceeds fullPct. Important An exception occurs when you specify incrPct as 0 and EMPTY NO, in which case BMC AMI Copy makes a copy even if there are no changed pages if BMC AMI Copy is able to acquire a registration point. FULL AUTO FULLPCT (incrPct,0) or CHANGELIMIT(incrPct,0) allows you the flexibility to make an incremental copy or no copy at all. If the percent of changed pages is greater than incrPct, an incremental copy will be made, if not escalated to a full copy for other reasons. 0 in fullPct prevents escalation to a full copy based on changed pages. Otherwise, no copy will be made. FULL AUTO FULLPCT(.01) or CHANGELIMIT(.01) allows the flexibility to make a full copy or no copy based on changed pages. If any pages have changed since the last image copy, BMC AMI Copy will report a minimum of 0.01 percent changed pages and will make a full copy. Because BMC AMI Copy analyzes open log ranges to determine if any changes have been made since the last copy, RESETMOD YES is not required in this case. Also, consider the following information when you use this option: - If the (incrPct, fullPct) format is used, it is possible that BMC AMI Copy will not make an image copy at all. Therefore, BMC AMI Copy will determine the percent of changed pages before QUIESCE processing to avoid dynamic allocation of the output data set. If the (fullPct) format is used, the estimate will occur after QUIESCE processing.
- If FULL AUTO FULLPCT (fullPct) is specified and there are no changed pages, BMC AMI Copy registers an incremental copy only if you specified the FULL AUTO EMPTY NO option and BMC AMI Copy was able to acquire a registration point.
- The parentheses around incrPct and fullPct are optional and are shown in the text above for clarity.
- When two values are used with FULLPCT, which means that a copy might not be made, and you are using stacked tape for your copies, you must use dynamic allocation. Otherwise, the VOL=REF of a copy could refer to a previous copy data set that was not actually created if a copy was not made.
- When FULLPCT (incrPct, fullPct) is used with SHRLEVEL CONCURRENT and with GROUP YES specified or implied, only those spaces in the group with a percentage of changed pages greater than incrPct will be copied.
- See Specifying-conditional-image-copies for examples of its use, or see the example Example-20-Using-MODIFY-to-delete-uncataloged-copies
Use FULL AUTO FULLPCT in conjunction with READTYPE RANDOM (the default) to optimize incremental copy performance. Typically, when changed pages exceed 15 percent, the time taken to make an incremental copy using READTYPE RANDOM is greater than the time taken to make a full copy. Warning Using FULL AUTO FULLPCT in conjunction with READTYPE FULLSCAN for successive incremental copies is not recommended—eventually, escalation will always occur because the modified page indicators are never reset—READTYPE FULLSCAN requires RESETMOD NO. Refer to Escalation-due-to-exceeding-a-percentage-threshold-for-changed-pages for information about why you might want to use the FULLPCT option. Also, see ICAUTOI=A and FULLPCT=50 for more information.
|
|---|
MAXINCRS integer | Specify MAXINCRS integer with FULL AUTO or CHANGELIMIT to tell BMC AMI Copy to escalate the request to a full image copy if the number of non-merged (CUMULATIVE NO) incremental copies made since the last full copy reaches integer. When calculating integer, BMC AMI Copy counts merged CUMULATIVE YES RESETMOD NO copies as one and each non-merged CUMULATIVE NO copy as one. Valid values of integer are 1 through 100. If you do not specify MAXINCRS, the value of the installation option MAXINCRS is used. The default value of the MAXINCRS installation option is 6. Refer to Escalation-due-to-limiting-the-number-of-incremental-copies for information about when to use this option. |
|---|
EMPTY | Use the EMPTY option with FULL NO, FULL AUTO, or CHANGELIMIT to specify whether to make and register an 'empty' incremental copy, that is, one in which no changed pages are found. Values of EMPTY | |
|---|
| (Default) EMPTY YES specifies that if no changed pages are found, BMC AMI Copy will leave the output empty and bypass registering the copy. Although the copy is not registered, the empty data set is allocated. | | Specify EMPTY NO to direct BMC AMI Copy to create and register an output data set with minimal data, even if no pages changed since the last copy of the same type. Important When you specify the EMPTY NO option, if BMC AMI Copy is unable to acquire a registration point for an incremental image copy, BMC AMI Copy bypasses the copy rather than create an image copy Refer to Registering-empty-incremental-copies for more information. |
|
|---|
CUMULATIVE | Use the CUMULATIVE option with FULL NO, FULL AUTO, or CHANGELIMIT to specify whether to include changed pages from the most recent prior RESETMOD NO incremental copy in the currently requested incremental copy. Values of CUMULATIVE | |
|---|
| (Default) CUMULATIVE YES tells BMC AMI Copy to include in the requested incremental copy all of the changed pages back to the latest full image copy or RESETMOD YES incremental copy. BMC AMI Copy copies all pages with the modification indicator set in the associated space map page. CUMULATIVE YES allows BMC AMI Copy jobs used with prior releases to run without change. Warning When you use the MERGECOPY utility provided with Db2 with RESETMOD NO CUMULATIVE YES KEEP YES incremental copies, MERGECOPY abends due to an incompatibility between BMC AMI Copy and the MERGECOPY utility. Instead of MERGECOPY, you can use the BMC AMI Recover product to correctly handle RESETMOD NO CUMULATIVE YES KEEP YES copies. For more information, see the BMC AMI Recover for Db2 documentation. Use the KEEP option with FULL NO, FULL AUTO, or CHANGELIMIT to specify whether to delete the entry for the most recent prior incremental copy (if it was a merged copy) from the SYSIBM.SYSCOPY table. KEEP is valid only when CUMULATIVE YES is in effect. KEEP YES (Default) KEEP YES tells BMC AMI Copy to keep the entry for the most recent prior (merged) incremental copy in the SYSIBM.SYSCOPY table. After you specify KEEP YES, you can reinstate that copy at any time using the RECALL command. Refer to Keeping-and-recalling-merged-incremental-copies for more information. KEEP NO Specify KEEP NO to delete the entry in the SYSIBM.SYSCOPY table for the most recent prior (merged) incremental copy.
| | Specify CUMULATIVE NO when you do not want to include the changes from the most recent prior incremental copy in the requested incremental copy or if you never reset the modification indicators. A CUMULATIVE NO copy contains only the changes made since the last copy and provides a true incremental copy even when RESETMOD NO is used. Important CUMULATIVE NO is valid only with RESETMOD NO. |
|
|---|
READTYPE | Use the READTYPE option with FULL NO, FULL AUTO, or CHANGELIMIT to help optimize the time required to make an incremental copy. READTYPE allows you to select the best I/O technique for examining the specified table spaces for changed pages, or to tell BMC AMI Copy to make the selection for you. Values of READTYPE | |
|---|
| (Default) READTYPE RANDOM specifies the conventional method of making incremental copies, which uses random I/O techniques. Typically, this method is most efficient when changed pages are below about 12 percent. Warning If you perform a recovery using a copy made with RESETMOD NO, you must make a full copy using RESETMOD YES before making any more incremental copies using the default READTYPE RANDOM. Failure to do so might result in data loss. | | Specify READTYPE FULLSCAN to tell BMC AMI Copy to use full table space scan techniques to identify the changed pages to include in the incremental copy. Use READTYPE FULLSCAN when you know that the space has had sufficient activity to make random reading inefficient. Typically, this method is most efficient when changed pages are greater than about 12 percent. READTYPE FULLSCAN is valid only with RESETMOD NO. Use READTYPE FULLSCAN for incremental copies when you use RESETMOD NO for the full copy. Important If a table space is defined with TRACKMOD NO, READTYPE FULLSCAN and RESETMOD NO are automatically set. | | Specify READTYPE AUTO when you want BMC AMI Copy to determine the I/O technique to be used for this incremental copy based on the number of changed pages, as shown by the modification indicators in the space map pages. The default is the READPCT installation option. If you specify READTYPE AUTO and RESETMOD NO, BMC AMI Copy selects either random I/O or READTYPE FULLSCAN. However, if you specify READTYPE AUTO and RESETMOD YES, BMC AMI Copy can select only random I/O. | | Specify READPCT to override the default percentage of pages (based on changed page indicators) that must change before escalation can occur from random I/O to full table space scan. The default is the value of the READPCT installation option, which defaults to 10%. Important READPCT is not valid for table spaces with the TRACKMOD NO attribute. |
|
|---|
MINPAGES integer | Use MINPAGES integer with FULL AUTO or CHANGELIMIT to specify the minimum number of pages that must exist in a space or partition before an incremental copy is considered. If the space or partition has less than integer pages, a full copy is made. If you do not specify MINPAGES, BMC AMI Copy uses the value of the MINPAGES installation option. The default value of the MINPAGES installation option is 180. MINPAGES is evaluated after the percentage of changed pages if two values (fullPct and incrPct) are given for either FULLPCT or CHANGELIMIT. Two values given for FULLPCT or CHANGELIMIT allows either no copy to be made if the first value is not exceeded, or a full copy to be made for 'small' spaces. If only a single value is given, a 'small' space would always be a full copy. |
|---|
FULLDAY dayName | Use FULLDAY dayName with FULL AUTO or CHANGELIMIT to specify the day of the week on which a full copy should always be made. Valid values are: - SUNDAY
- MONDAY
- TUESDAY
- WEDNESDAY
- THURSDAY
- FRIDAY
- SATURDAY
You can abbreviate values to a minimum of the first three characters. Important This option takes precedence over all other FULL AUTO and CHANGELIMIT options (regardless of the changed pages percentages). |
|---|
MAXFULLDAYS value | Use MAXFULLDAYS value with FULL AUTO or CHANGELIMIT to specify the maximum number of days allowed since the previous full image copy. You can use up to two decimal places in the value that you specify. If a FULL AUTO or CHANGELIMIT image copy runs when the previous full image copy is more than the value of MAXFULLDAYS ago, BMC AMI Copy escalates the request to a full image copy. If you specify both the MAXFULLDAYS and the FULLDAY options, either can cause escalation to a full image copy. Consider the following example: COPY TABLESPACE MYDB.MYTS
FULL AUTO FULLDAY MONDAY MAXFULLDAYS 7 If the request above runs on Monday, escalation to a full image copy occurs. If the request runs on any day other than Monday, escalation to a full image copy will occur if the previous full image copy was created more than 7 days ago. |
|---|
SMARTSTACK | The SMARTSTACK tells BMC AMI Copy whether or not BMC AMI Copy stacks incremental copies in the same logical stacking order as their associated full copies. If you do not specify SMARTSTACK on the COPY command, BMC AMI Copy uses the value of the SMARTSTK installation option as the default. Important You can also specify SMARTSTACK on the OPTIONS command. Values of SMARTSTACK | |
|---|
| Specifying SMARTSTACK YES tells BMC AMI Copy to analyze the stacking order for the associated full copies and stack the incremental copies in the same order. Important SMARTSTACK YES forces GROUP YES. | | Specifying SMARTSTACK NO tells BMC AMI Copy that no stacking analysis for incremental copies will be done. They will be stacked as they are processed. |
|
|---|
FULLRESET | The FULLRESET option changes SHRLEVEL CHANGE RESETMOD NO copies to use RESETMOD YES when 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. If you do not specify FULLRESET on the COPY command, BMC AMI Copy uses the value of the FULLRESET installation option (FULLRESET=NO) as the default. Important You can also specify FULLRESET on the OPTIONS command. Values of FULLRESET | |
|---|
| When you specify 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. 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 FULL AUTO RESETMOD NO or CHANGELIMIT SHRLEVEL CHANGE RESETMOD NO, specifying FULLRESET NO does not convert copies to use RESETMOD YES when BMC AMI Copy makes full copies. |
|
|---|