Generating drop recovery output

This topic includes the following procedures:

After you complete the steps to specify one form of output, you can specify additional forms of output, as described in this section, or skip to one of the following procedures:

• Specify skeleton JCL to recover data from a source outside of Db2 (see Creating JCL to restore data from a source outside of Db2 ).

• Generate the JCL for the automated drop recovery step and submitting the job (see Creating a batch job from a work ID).

Before you begin

To generate a Drop Recovery report

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the Drop Recovery Report field. Press Enter.

   Log Master displays the Report Destination Options panel.

2. Choose a report destination and press Enter.

   Log Master displays an output information panel.

3. Specify the data set or SYSOUT options required to process the report in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.

   The options that you specified appear under the Drop Recovery Report field.

4. (optional) To use a template for the Drop Recovery report, type E in the Drop Recovery Report field and press Enter.

   Log Master displays a panel on which you can choose to use a report template stored in the Repository, or a template defined in a data set. For more information about using a report template, see Creating a customized report template. 

To generate DDL statements that re-create dropped objects

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the Recreate DDL field. Press Enter.

   Log Master displays the Output Dataset Information panel.

2. Specify the data set options required to allocate a data set in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.
3. To include statements in the generated JCL that execute the generated DDL statements, type Y in the Execute DDL field.
4. (optional) To specify an authorization ID to execute DDL statements that is different than the ID that submits the job, type an authorization ID in the Set SQLID field.

   Log Master generates a SET CURRENT SQLID statement and inserts it at the start of the generated DDL statements.

5. (optional) To specify an authorization ID used to bind programs and generate application plans that is different than the ID that submits the job, type an authorization ID in the Bind Owner field.

   Log Master uses this authorization ID to bind an application plan when the product executes DDL statements. If you do not specify a value, Log Master uses the value of the BINDOWN installation option. If the installation option value is not specified, Log Master uses the user ID of the person that submitted the job. 

To generate BMC AMI Recover syntax

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the BMC Recover field. Press Enter.

   Log Master displays the Output Dataset Information panel.

2. Specify the data set options required to allocate a data set in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.

   Log Master allocates two data sets, RECOVER and RECOVER2 outputs.

   • RECOVER output has BMC AMI Recover syntax for the recovery of the table spaces and tables.

   • RECOVER2 has BMC AMI Recover syntax for the recovery of the clones.

   Specify the RECOVER data set here and RECOVER2 will use the same attributes as the RECOVER data set. The naming convention for RECOVER2 is based on the RECOVER data set model. For more information, see the RECOVER DATASET Output definition.

3. To include statements in the generated JCL that cause Log Master to run BMC AMI Recover using the generated syntax, type Y in the Execute Recover field.
4. Specify whether the syntax should include the LOGONLY option.

   This option directs BMC AMI Recover to use only data from log records to perform the recovery, and it applies to all of the Db2 objects in the current automated drop recovery action.

   • To use image copies to recover the data, type N. This is the default value.

   • To avoid using image copies (if you intend to recover the table space data set outside of the automated drop recovery job stream), type Y.

5. Specify whether the OUTCOPY syntax should use the ASCODED or BYPART option.

   Depending on the image copies that Log Master selects as input sources for the automated drop recovery, BMC AMI Recover can create separate output image copies for each partition, or create one combined image copy for the entire table space. This option applies to all table spaces that you are recovering.

   • To create output image copies in the same format (either DSNUM 0 or partitioned) as the input image copies, type A.

     To determine the format of the input image copies, see the Drop Recovery report.

   • To create an output image copy for each partition in the table space (regardless of the format of the input image copies), type B.

6. To specify the data set names for your output image copies, access the Dropped Object Name Maintenance panel and type O in the ACT field of the table space.

   Important

   Ensure that you specify data set names for your output image copies before you execute the automated drop recovery.

To generate DSN1COPY syntax to recover a table space

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the DSN1COPY field. Press Enter.

   Log Master displays the Output Dataset Information panel.

2. Specify the data set options required to allocate a partitioned data set (PDS) in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.

   The data set must be a PDS to contain multiple members that Log Master generates.

3. Verify that the Execute Copy field contains a value of Y.
4. Type D in the Recovery Type field and press Enter. 

To generate post-recovery SQL statements that move table data

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the Post Recover SQL field. Press Enter.

   Log Master displays the Output Dataset Information panel.

2. Specify the data set options required to allocate a data set in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.
3. To include statements in the generated JCL that cause Log Master to execute the generated SQL statements, type Y in the Execute SQL field.

   When the SQL statements are executed, they migrate data from a temporary table used during the recovery process to the recovered version of the original table.

To generate Db2 commands that rebind plans

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the Post Recover Rebinds field. Press Enter.

   Log Master displays the Output Dataset Information panel.

2. Specify the data set options required to allocate a data set in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.
3. To include statements in the generated JCL that cause Log Master to execute the generated DB2 BIND commands for the recovered objects, type Y in the Execute Rebinds field. 

To generate Db2 utility commands to take table spaces out of check pending status

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the Post Recover Checks field. Press Enter.

   Log Master displays the Output Dataset Information panel.

2. Specify the data set options required to allocate a data set in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.
3. To run the generated JCL to take the table spaces out of check pending status, type Y in the Execute Checks field.

   Log Master generates the default DDNAME specifications for SYSUT1, SORTOUT and SYSERR in the JCL. For the UNIT value, Log Master uses the value of the WKUNIT installation option, if specified, or SYSALLDA. 

To generate RUNSTATS commands

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the Post Recover Runstats field. Press Enter.

   Log Master displays the Output Dataset Information panel.

2. Specify the data set options required to allocate a data set in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.
3. To include statements in the generated JCL that cause Log Master to execute the generated RUNSTATS commands for the recovered object, type Y in the Execute Runstats field. 

To generate REPAIR commands to update versions of recovered objects

1. On the Generate Automated Drop Recovery panel, in the Specify Outputs Desired section, type E in the Post Recover Repairs field. Press Enter.

   Log Master displays the Output Dataset Information panel.

2. Specify the data set options required to allocate a data set in your environment, and then press F3 to return to the Generate Automated Drop Recovery panel.
3. Type Y in the Execute Repairs field.

   This step includes statements in the generated JCL that cause Log Master to execute the generated REPAIR commands for the recovered object.