INDEXLOG=NO

This option specifies the behavior of RECOVER INDEX has. Valid values are NO, YES, and AUTO.

• NO—(Default) Indicates that RECOVER INDEX and REBUILD INDEX are synonyms, and indexes are rebuilt from the keys extracted from the table space.
• YES—RECOVER INDEX recovers indexes from copies, the log, or both, while REBUILD INDEX rebuilds indexes from the keys extracted from the table space.
• AUTO—RECOVER INDEX first attempts an index recovery from image copies, the log, or both. However, if an image copy for the index does not exist, BMC AMI Recover converts the request to a REBUILD INDEX request.

INDEXLOG=AUTO supports BACKOUT recoveries. However, conversion from RECOVER INDEX to REBUILD INDEX is not supported for the following options:

• 
  
  • OUTCOPY: REBUILD INDEX does not include the OUTCOPY option so this request is not eligible for conversion.
  • OBIDXLAT: REBUILD INDEX does not include the OBIDXLAT option, so this request is not eligible for conversion.
  • TOLOGPOINT: If the RECOVER INDEX request includes the TOLOGPOINT option, the request is eligible for conversion to REBUILD INDEX only if the associated table space is also recovered in the same job step.
  • TOCOPY: If the RECOVER INDEX request includes the TOCOPY option, the request is eligible for conversion to REBUILD INDEX only if the associated table space is also recovered in the same job step.
  • DSNUM: If the RECOVER INDEX command statement was for a specific data set of a nonpartitioned index, the request is not eligible for conversion to REBUILD INDEX.

You can override the INDEXLOG installation option by using the INDEXLOG keyword with the OPTIONS command.