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

RECALL syntax options

The following RECALL syntax options are available.

RECALL SYNTAX options


Option

Description

APPLICATION creatorName

APPLICATION creatorName can be used to specify the object for the RECALL command. When this type of object is specified with a creator name of SAPR3, all table spaces that have CREATOR=SAPR3 are selected.

APPLICATION can be mixed with TABLESPACE specifications within the same RECALL command.

ATLOGPOINT X’hexStartLRSN’

Use the ATLOGPOINT option to provide the LRSN of the incremental copy (or copies) you want to reinstate. Use ATLOGPOINT in a data sharing environment.

Important

The ATRBA and ATLOGPOINT options of RECALL provide similar functions for non-data-sharing and data sharing environments, respectively. They are alternatives and cannot be used together in the same RECALL statement.

ATRBA X’hexStartRBA’

Use the ATRBA option to provide the RBA of the incremental copy (or copies) you want to reinstate. Use ATRBA in a non-data-sharing environment.

CLONE

Use the CLONE option to reinstate an incremental image copy for only the specified clone table space.

The base table space and its clone can not be processed in the same BMC AMI Copy command.

DSNUM

Use the DSNUM option to identify either a partition (or data set) in the table space named in the TABLESPACE option, or all of the partitions (or data sets) contained in that table space. The default is all of the partitions or data sets (DSNUM ALL).

Values of DSNUM

Value

Description

DSNUM integer

DSNUM integer is the number of a single data set or partition in the table space for which you made an incremental copy (or copies) and you now want to reinstate. Specify this option when you want to reinstate an incremental image copy of only one data set or partition in that table space.

For a partitioned table space, integer is the partition number. For a nonpartitioned table space, integer is the ordinal number of the data set.

DSNUM begin:end

DSNUM begin : end specifies a range of partitions to process. You specify the range of partitions with two numbers separated by a colon (:) with or without spaces. The following example gives a specification that copies physical partitions 10 through 20:

 RECALL TABLESPACE ACCOUNTS.*
DSNUM 10:20

During the table space selection process, only partitioned table spaces that overlap the partition range qualify for selection. Nonpartitioned and partitioned table spaces that do not have as many partitions as the low value of the range do not qualify for selection, and BMC AMI Copy issues the following message:

 BMC47431I databaseName.tableSpaceName DID NOT QUALIFY FOR RANGE SELECTION

LOGICAL

Adding the LOGICAL option after a DSNUM begin: end specification allows you to indicate logical partitions rather than physical partitions and have the logical partitions mapped to their respective physical data set numbers. BMC AMI Copy then continues as if you specified a physical range of partitions. You might use the LOGICAL option if you have rotated your partitioned table spaces to create a logical view of the physical data sets.

In the following specification, the logical partition numbers 10 through 20 are mapped to their respective physical data set numbers:

 RECALL TABLESPACE ACCOUNT.*
DSNUM 10:20 LOGICAL

DSNUM ALL

DSNUM ALL is the default and specifies that you want to reinstate an incremental copy (or copies) of all of the partitions or data sets in the table space named in the TABLESPACE option.

EXCLUDE

Use the EXCLUDE option after a wildcard table space specification to exclude one or more table spaces from reinstatement. You can use the wildcards % and * or specific names to specify the exclusions.

The excluded spaces must be in the form of a list, following the EXCLUDE keyword. Each item in the list must be in the form databaseName.tableSpaceName and you must separate the individual items by commas. Optionally, you can enclose the list in parentheses. Excluding-specified-spaces-from-a-wildcard-specification provides more information.

INDEXSPACE OBJECTSET objectSetName

INDEXSPACE OBJECTSET can be used in place of INDEXSPACE in any RECALL command to specify the index spaces included in a BMC AMI Recovery Manager group. The BMC AMI Recovery Manager group is specified by objectSetName.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager groups, see the BMC AMI Recovery Manager for Db2 documentation

Important

DSNUM cannot be used with a BMC AMI Recovery Manager group in BMC AMI Copy. Group objects are copied using the DSNUM specified in the BMC AMI Recovery Manager group. However, EXCLUDE is supported.

OBJECTSET objectSetName

Use OBJECTSET objectSetName to specify the table spaces and index spaces that are included in the BMC AMI Recovery Manager group identified by objectSetName.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager groups, see the BMC AMI Recovery Manager for Db2 documentation.

ON ERROR BADSTATUS

The ON ERROR BADSTATUS option allows you to specify what action BMC AMI Copy is to take if a space or partition is in an unacceptable status or has a BMC or Db2 utility running against it.

Values of ON ERROR BADSTATUS

Value

Description

ON ERROR BADSTATUS END

ON ERROR BADSTATUS END, the default, indicates BMC AMI Copy is to terminate processing with a RC=12.

ON ERROR BADSTATUS SKIP

ON ERROR BADSTATUS SKIP causes BMC AMI Copy to issue a message, skip over the space, and continue processing other spaces specified in SYSIN.

If a space is skipped because of ON ERROR BADSTATUS SKIP, the space will not be retried if the job abends and you retry the job with a NEW/RESTART.

ON ERROR NOTSUPPORTED

The ON ERROR NOTSUPPORTED option allows you to specify what action BMC AMI Copy is to take if a space or partition is an unsupported type in BMC AMI Copy.

Values of ON ERROR NOTSUPPORTED

Value

Description

ON ERROR NOTSUPPORTED END

ON ERROR NOSUPPORTED END, the default, indicates BMC AMI Copy is to terminate processing with a RC=12 if an unsupported type is encountered.

ON ERROR NOTSUPPORTED SKIP

ON ERROR NOTSUPPORTED SKIP causes BMC AMI Copy to issue a message, skip over the space, and continue processing other spaces specified in SYSIN.

 TABLESPACE databaseName.spaceName or INDEXSPACE databaseName.spaceName

Use TABLESPACE or INDEXSPACE to specify the spaces for which one or more incremental copies must be reinstated. The space specification is a list of which can contain both explicit space names and wildcard patterns with the individual items in the list separated by commas. The COPY keyword is implicit and is not required.

When you use a wildcard specification, you can also use the EXCLUDE option to specify any spaces you want to exclude from reinstatement.

Important

The copy must have been made using KEEP YES. If you specified KEEP NO for the copy, you cannot use the RECALL command.

Each explicit space name in the space list must be in the form databaseName.spaceName where:

  • databaseName is the name of the database containing the space. If you do not provide a database name, BMC AMI Copy uses the default, DSNDB04.
  • spaceName is the name of the space containing the data sets or partitions for which the copy (or copies) was made.

You can enclosedatabaseName.spaceName in double quotation marks or single quotation marks. This allows use of special characters, such as $, #, or /, in your object names.

When you use a wildcard pattern to specify multiple spaces, you can include the wildcard characters * (asterisk) and % (percent) to provide matching on one or more characters. Using-wildcard-characters-in-the-object-name-specification tells you how wildcards are used and how BMC AMI Copy orders the results of wildcard expansions.

You can also use the special wildcard DB2CATALOG to reinstate hidden incremental copies of Db2 catalog and directory spaces. However, because BMC AMI Copy does not make incremental copies of special case catalog and directory tables, BMC AMI Copy excludes such spaces when you use this wildcard.

TABLESPACE OBJECTSET objectSetName

TABLESPACE OBJECTSET can be used in place of TABLESPACE in any RECALL command to specify the table spaces included in a BMC AMI Recovery Manager group. The BMC AMI Recovery Manager group is specified by objectSetName.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager groups, see the BMC AMI Recovery Manager for Db2 documentation.

Important

DSNUM cannot be used with a BMC AMI Recovery Manager group in BMC AMI Copy. Group objects are copied using the DSNUM specified in the BMC AMI Recovery Manager group. However, EXCLUDE is supported.

RMGROUP creator.groupName

RMGROUP can be used in place of TABLESPACE in any RECALL command to specify the table spaces in a BMC AMI Recovery Manager group.

RMGROUP is followed by the two-part BMC AMI Recovery Manager creator.groupName. A maximum of 8 characters can be used for creator, while groupName can be a maximum of 18 characters. creator follows the rules for short SQL identifiers. groupName follows the rules for long SQL identifiers. Each part, creator, and groupName can be delimited by double or single quotation marks. The symbols $, #, and @ are valid and can be used as the first character for creator.

BMC AMI Copy does not allow wildcards to be specified with RMGROUP and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager groups, see the BMC AMI Recovery Manager for Db2 documentation.

Important

DSNUM cannot be used with a BMC AMI Recovery Manager group. Group objects are copied using the DSNUM specified in the BMC AMI Recovery Manager group. However, EXCLUDE is supported.


Related topic

RECALL-command



 

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