Skip to Content
Information
Limited support BMC 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.

QUIESCE object list

This section describes options used to specify the object list for the QUIESCE command.

QUIESCE object list options 

Option

Description

APPLICATION creatorName

APPLICATION can be used to specify the objects for the QUIESCE 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 QUIESCE command.

OBJECTSET objectSetName

Use OBJECTSET objectSetName to copy 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

RMGROUP creator.groupName

RMGROUP can be used in place of TABLESPACE in any QUIESCE command to specify the table spaces that are included 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. Each 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

Warning

Important

Only the table spaces are used from a BMC AMI Recovery Manager group. Any index spaces that appear in the group are ignored.

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

TABLESPACE databaseName.spaceName

Use the TABLESPACE option to specify the spaces you want to quiesce. The table space specification is a list that can contain both explicit space names and wildcard patterns with the individual items in the list separated by commas. BMC AMI Copy expands wildcards and passes through to the Db2 QUIESCE utility.

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

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

  • databaseName is the name of the database where the target space is located. If you do not provide a database name, BMC AMI Copy uses the default, DSNDB04.
  • tablespaceName is the name of the target space containing the partitions or data sets you want to quiesce.

You can enclose databaseName.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 quiesce Db2 catalog and directory spaces.

Warning

Important

The following conditions apply to the use of wildcards:

  • When you use * or % as wildcards to specify multiple spaces, BMC AMI Copy excludes spaces in DSNDB01, DSNDB06, DSNDB07 and other work file databases to avoid unintentional copying of catalog, directory, and temporary databases. Also, when you use the DB2CATALOG wildcard, BMC AMI Copy excludes DSNDB07 and other work file databases.
  • If the wild card pattern results in no matches, BMC AMI Copy will issue a warning.

TABLESPACE OBJECTSET objectSetName

TABLESPACE OBJECTSET can be used in place of TABLESPACE in any QUIESCE command to specify the table spaces that are included in a BMC AMI Recovery Manager group.

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.

Warning

Important

Only the table spaces are used from a BMC AMI Recovery Manager group. Any index spaces that appear in the group are ignored.

Also note, that 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

QUIESCE-command



 

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

BMC AMI Copy for Db2 12.1