Skip to Content
Information

This site will undergo maintenance on Friday, 26 September at 2:00 AM CDT / 12:30 PM IST and may experience a short period of instability during that time.

Operational considerations for secondary indexes—Reorg function (Fast Reorg Facility/EP)

If the database has secondary indexes, you have the following choices in how the Reorg function handles them:

  • Use the same (old) data set names for output.
    You must ensure the secondary index data sets are empty (by using DELETE/DEFINE in a previous step) before the Reorg function tries to use them. You must specify SHARE(NO).
  • Preserve the original index data sets and use temporary data sets for output.
    To preserve the original index data sets that are associated with the disorganized database, use new data set names. The Reorg function recognizes that the index data sets with new names are reorganized data sets, and the Reorg function includes them in the swap process. The primary reason you would do this is to ensure that you can easily fall back to the prereorganization status of the database if you encounter problems during or after the reorganization process, or if you specify SHARE(YES).

Related topic

Operational-considerations

If any output data sets are not empty, the Reorg function issues an error message and the job step terminates.

If a reorganization fails and you specified SHARE(NO) and used old data set names for the secondary index data sets, your original indexes will be corrupted. The secondary index files will be empty or will not match the database before the start of the reorganization process.

To get indexes identical to the ones you had before beginning the reorganization, you must perform one of the following tasks:

  • Recover the secondary index files.

  • Use the Index Build function to scan the disorganized primary database and build the secondary index files.

    Warning

    Note

    If you specified INPUT(UNLDFILE), the disorganized primary database is no longer intact. Use the image copy that you took before the reorganization.

You can prevent the loss of the secondary indexes of the disorganized database by taking either of the following actions:

  • Specify different data set names in the JCL for the reorganized secondary index data sets.
  • Rename the original secondary index files, or make a backup of the original secondary index files.

 

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

BMC AMI Online Reorg for IMS 5.2