Creating JCL to restore data from a source outside of Db2

To recover data from a source outside of Db2, you can specify skeletal JCL to accomplish the recovery.

For example, you might need to restore the recovered objects from a DASD pack backup. Use this procedure to tell BMC AMI Log Master where to access the JCL necessary to restore the data from the outside source.

Related topic

Recovering-dropped-objects

To specify your own JCL for recovery

  1. Create a PDS member that contains JCL statements to restore the data from your backups outside of Db2.BMC AMI Log Master treats this member as an ISPF skeleton. You must store the member in a data set that is in the ISPSLIB DD name concatenation of your TSO procedure.

    Within an ISPF skeleton, you have the option to access certain ISPF variables within your JCL. The ALPSJCL member in the HLQ.DBPLIB library contains ISPF variables that you can use in your skeleton member (where HLQ represents a high-level qualifier that is assigned in your environment during installation). All JCL statements in your member must adhere to ISPF file tailoring rules. For more information about file tailoring, see the appropriate ISPF technical documentation from IBM.

  2. On the Generate Automated Drop Recovery panel, in the Non-DB2 Restore field, specify the name of the PDS member that contains your JCL.BMC AMI Log Master incorporates your JCL within its generated JCL. BMC AMI Log Master inserts your recovery JCL after the STOPCMDS job step. When you generate and run the job, the product runs your JCL to perform data recovery for the specified objects.

 

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