Delete and redefine databases with IDCAMS definitions

You provide information in the profile to control whether and how the function creates this JCL. For more information, see Profile Maintenance panel — page 8 and Profile Maintenance panel — page 9.

For the Create Recovery JCL function to create delete and define JCL, in the profile you must identify the location of the Access Method Services (AMS) delete and define information:

• The AMS DEL/DEF library--a single data set that contains both delete and define information
• The AMS DELETE library and AMS DEFINE library--separate data sets, one for delete information and one for define information

For either type of configuration, you can identify multiple data sets to be concatenated.

The AMS library (or libraries) must contain members with names that match the ddnames of the objects to be recovered or rebuilt. These members contain individual IDCAMS delete and define statements or OSAM TSO ALLOC statements, or they contain complete JCL to delete and define the database data sets.

The way that the Create Recovery JCL function creates the delete and define elements of the recovery job stream depends on the recovery utility you use and the contents of the AMS library:

• If you use the BMC Recovery utility, the Create Recovery JCL function includes the IDCAMS(*) keyword in the utility control statements, and it creates DD statements to identify the AMS library. The Recovery utility directly invokes IDCAMS to delete and define the database data sets.
• If you use the IMS Database Recovery utility and the AMS library contains IDCAMS or TSO ALLOC statements, the Create Recovery JCL function creates separate IDCAMS job steps.
• If you use the IMS Database Recovery utility and the AMS library contains delete/define JCL, the Create Recovery JCL function copies the JCL from the member into the recovery job stream.

If the profile specifies the AMS library and the Create Recovery JCL function does not find members that match the ddname, the function places the following block of comments in the IMS recovery JCL in place of the redefinition step:

If an OLR is possible for a PHIDAM HALDB that is being recovered, it might be necessary to create delete/define JCL for both X and Y primary indexes.