MODIFY Object list syntax

APPLICATION creatorName can be used with the MODIFY command to specify application-owned objects, such as those owned by an SAP R/3 application. When this keyword is specified with a creator name of SAPR3, the MODIFY command acts on all table spaces that have CREATOR=SAPR3. If INDEXES YES is specified, MODIFY also acts on all indexes for the selected table spaces.

APPLICATION can be mixed with other object specifications within the same MODIFY command.

Use INDEXSPACE OBJECTSET objectSetName to modify all index spaces that are included in the BMC AMI Recovery Manager object set identified by objectSetName.

The following rules apply to the use of INDEXSPACE OBJECTSET:

• BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages about 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 object sets, see the BMC AMI Recovery Manager for Db2 documentation.

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

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages about 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 object sets, see the BMC AMI Recovery Manager for Db2 documentation.

Use the TABLESPACE option to specify the table spaces and (optionally) any indexes on those table spaces that you want to maintain. Use the INDEXSPACE option to specify any indexes you want to maintain independently of their related table spaces. The space specification is a list that may contain both explicit space names and wildcard patterns with the individual items in the list separated by commas. When you use a wildcard specification, you can use the EXCLUDE option to specify any table or index spaces you want to exclude from maintenance.

Each explicit 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, MODIFY uses the default, DSNDB04.
• spaceName is the name of the target space containing the partitions, data sets, or indexes you want to maintain.

Optionally, you can enclose databaseName.spaceName in double quotation marks (').

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. The characters * and % can each represent up to eight characters and are treated as equivalent by the MODIFY command.

Use TABLESPACE OBJECTSET objectSetName to modify all table spaces that are included in the BMC AMI Recovery Manager object set identified by objectSetName.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages about 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 object sets, see the BMC AMI Recovery Manager for Db2 documentation.

RMGROUP can be used as an alternative object specification in any MODIFY command. RMGROUPTS is also accepted as an alternative to RMGROUP.

RMGROUP is followed by the two-part BMC AMI Recovery Manager object set name. Each explicit name in the RMGROUP list must be in the form creator.groupName where:

• creator is a maximum of 8 characters and follows the rules for short SQL identifiers.
• groupName can be a maximum of 18 characters and follows the rules for long SQL identifiers.

Each part, creator and groupName, can be delimited by double quotation marks (').

MODIFY does not allow wildcards to be specified with RMGROUP and will issue messages about 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 object set, see the BMC AMI Recovery Manager for Db2 documentation.

Use RMGROUPIX to identify index spaces that are included in a BMC AMI Recovery Manager object set.

RMGROUPIX is followed by the two-part BMC AMI Recovery Manager creator.groupName. A maximum of 8 characters can be used for a 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 a creator.

The MODIFY command does not allow wildcards to be specified with RMGROUPIX and will issue messages about 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 object sets, see the BMC AMI Recovery Manager for Db2 documentation.