Using the INDEXSPACE specification
You can create index image copies by using the INDEXSPACE specification with the COPY or COPY IMAGECOPY commands.
You can provide a single index space name or a list of index spaces. Wild cards can be used in the same way as with table spaces. For more information, see Using-wildcard-characters-in-the-object-name-specification.
If the IXSIZE option is non-zero, only those indexes that exceed IXSIZE are copied. For more information, see Copying-indexes-based-on-size.
When the INDEXSPACE specification is used with the COPY command, options that apply only to TABLESPACE are not applicable. Those options include:
- CHECKERROR
- CHECKTSLEVEL
- FULL and all of its suboptions
- INDEXES
- NACTIVE
- RESETMOD
- RUNSTATS
- SQUEEZE
For indexes, DSNUM has different implications than when it is used in copying table spaces. The value of the DSNUM option for index copies works with the value of the IXDSNUM installation option to influence how index copies are made. Valid values for IXDSNUM are DATASET and ALL. The default is set in the installation options module, which is delivered with IXDSNUM=ALL. DSNUM can be specified on either COPY TABLESPACE ... INDEXES YES or COPY INDEXSPACE.
To see how BMC AMI Copy handles index copies when these options are specified, see OPTIONS-syntax-option-description. The IXDSNUM installation option can be overridden at runtime by using IXDSNUM on the OPTIONS statement .
Grouping can be implied by repeating INDEXSPACE and any options under the same COPY statement. INDEXSPACE and TABLESPACE specifications can be mixed within a single COPY statement. If the statements are mixed, any options that apply only to a TABLESPACE are ignored for the INDEXSPACE. For more information, see Using-multitasking-with-GROUP-YES.
COPY IMAGECOPY INDEXSPACE is similar to COPY IMAGECOPY TABLESPACE except that it copies index copies. However, the following options are not allowed for indexes:
- CHECKTSLEVEL
- CHECKERROR
- SQUEEZE
Related topic