MODIFY Object options syntax

This section describes the Object options syntax and description for the MODIFY command. 

Related topic

MODIFY-command

MODIFY Object options syntax

3_MODIFY_command_object_options_syntax_SPE1911.png

Important

DSNUM PART or DSNUM DATASET parameters are no longer valid for MODIFY command. If you use DSNUM PART or DSNUM DATASET parameter, they get converted to DSNUM ALL.

MODIFY Object option description

Option

Description

CLONE

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

Use the CLONE option with MODIFY to delete SYSCOPY or BMCXCOPY records or SYSLGRNX records for only clone objects.

DSNUM

For table space maintenance, the DSNUM option identifies either a single partition or data set in the table space named in the TABLESPACE specification 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).


Important

DSNUM is not applicable to RMGROUP, OBJECTSET, or APPLICATION.

For index maintenance, MODIFY, by default, performs maintenance at the physical data set level (DSNUM DATASET). The DSNUM value specified works in conjunction with the IXDSNUM installation option to determine how indexes are handled.

Important

For details, see IXDSNUM. IXDSNUM can also be specified as an BMC AMI Copy installation option. For details, see IXDSNUM=ALL.

Values of DSNUM

Value

Description

DSNUM integer

For table space, the DSNUM integer specifies the number of a single partition or data set in the target table space that you want to maintain. For a partitioned table space, an integer is the partition number. For a nonpartitioned table space, an integer is the ordinal number of the data set. Specify this option when you want to perform maintenance on only one partition or data set in that table space.

For an index space, DSNUM integer is the number of a single data set in the target index space that you want to maintain. Specify this option when you want to perform maintenance for only one physical data set in that index space. For an index space, an integer is the ordinal number of the data set. However, for details on the effects of DSNUM integer in conjunction with the value of the IXDSNUM option on index handling, see the tables in IXDSNUM.

The value of the integer must be in the range 1 through 4096.

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 modifies physical partitions 10 through 20:

MODIFY 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:

 BMC47431IdatabaseName.tableSpaceName DID NOT QUALIFY FOR RANGE SELECTION

When you use the INDEXES YES option on the MODIFY command, the index space that is associated with the table space is also selected.

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:

MODIFY TABLESPACE ACCOUNT.*
       DSNUM 10:20 LOGICAL

For INDEXES YES and MODIFY INDEXSPACE, the conversion of the logical partition to the physical partitions is based on the parent table space.

EXCLUDE databaseName.spaceName

Use the EXCLUDE option after a wildcard space specification to exclude one or more spaces from maintenance processing that would otherwise be included. 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.spaceName and you must separate the individual items with commas. Optionally, you can enclose the list in parentheses.

Important

EXCLUDE processing is done in two passes for TABLESPACE specifications. The first pass excludes table spaces from the space list so that indexes for the excluded table spaces are not processed if INDEXES YES (see INDEXES (or INDEX)) is specified. A second EXCLUDE pass is performed after INDEXES YES is expanded to allow indexes to be excluded by name.

INDEXES

The INDEXES option allows you to specify that you want the MODIFY command to perform maintenance on any indexes defined for the table spaces specified by the TABLESPACE, RMGROUP, or APPLICATION option. The default is INDEXES NO indicating that no index maintenance is to be performed.

Important

The use of INDEX is synonymous with INDEXES for this option.

The INDEXES option is not applicable to the INDEXSPACE specification.

Values of INDEXES

Value

Description

INDEXES YES

Specifying INDEXES YES tells MODIFY to perform maintenance on all indexes defined for the table spaces specified by TABLESPACE, RMGROUP, OBJECTSET, or APPLICATION.

Important

For RMGROUP or TABLESPACE OBJECTSET specifications, any index spaces that appear in the group are ignored. The INDEXES YES option or the RMGROUPIX option may be used to select the indexes for the selected table spaces.

If you specify INDEXES YES and also specify DSNUM PART, DSNUM ALL, DSNUM integer, or DSNUM DATASET, MODIFY uses the IXDSNUM option, in conjunction with the DSNUM value specified, to determine how to handle indexes. For details, see IXDSNUM.

Important

IXDSNUM can also be specified on the BMC AMI Copy OPTIONS statement. See IXDSNUM.

INDEXES YES implies grouping with the table space. Indexes on a table space are processed immediately after the table space. The indexes are processed in alphanumeric order and data set order.

Important

When you specify INDEXES YES, an index will be included only once within the same SYSIN. If you need to process it more than once, you must use an INDEXSPACE specification (see INDEXSPACE) or process the index in a separate step.

INDEXES NO

Specifying INDEXES NO, which is the default, tells MODIFY that no maintenance is to be performed on indexes on the specified table spaces.


 

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