Establishing a recovery point and creating an archive log

It also causes the creation of an archive log for all Db2 members.

About the archive log command

You can use the archive log creation program, ARMBLOG, to issue the appropriate archive log command and wait for the offload to finish.

For more information about ARMBLOG, see ARMBLOG—Archive log creation.

You can also issue the -ARCHIVE LOG command manually. If you issue the command manually, select the appropriate environment type in the following table and perform the associated step.

Before you begin

To establish a recovery point, you need the following authorizations:

• To create the JCL: EXECUTE authority for BMC AMI Recovery Manager
• To execute the JCL:
  • APF authority for ARMBCRC
  • READ authority for BSDS data sets
  • ALTER authority for the active log data sets

To establish a recovery point and create an archive log

1. In the BMC AMI Recovery for Db2 Main Menu select 3. System Resources.
2. In the System Recovery and JCL Generation panel, select Disaster Recovery Prep.
3. In the Disaster Recovery panel, select Establish a Recovery Point.
4. In the Establish Recovery Point panel, choose the subsystem recovery point. For more information, see the following table.

5. Specify the ARMBLOG options as follows and press Enter:

   • Number of times to check for offload complete (defaults to 5)

   • Number of seconds to wait before re-checking for offload complete (defaults to 180 seconds)

     The System Resource Recovery and Maintenance panel is displayed again.

   The System Resource Recovery and Maintenance panel is displayed again.

6. At this point, you can generate the JCL to establish the recovery point, or you can wait until you have also set options for preparing the archive logs and subsystem recovery and then generate JCL for all three steps into a single job.
   1. To generate the job now, select Establish a Recovery Point (ARMBLOG or ARMBCRC), and then press Enter.
   2. To generate a single job for all three disaster recovery steps, set all options, then select Option 9, Generate ALL Disaster Recovery Jobs, and then press Enter.
7. On the JCL Specification panel, enter a fully qualified output data set name. Be aware of the following information:
   • The output data set is used for saving the JCL and must be cataloged. If not enclosed in quotes, the output data set will be prefixed by your TSO prefix.
   • The job statement must contain a symbolic variable (&#) for the job number. See Output-data-sets-job-cards-and-symbolic-variables for more information.

8. Save the JCL data set or submit the job as required.

   Option	Description
   End of the archive log created using the ARMBLOG program	Generates JCL to run the ARMBLOG program, which performs an -ARCHIVE LOG command The timestamp of the -ARCHIVE LOG command then becomes the point of recovery.
   User specified timestamp, using the ARMBCRC program	Specifies a timestamp to be used as the point of recovery Important The timestamp recorded in the CRRDRPT table must be equal to or less than the current time. If you enter a timestamp greater than the current time (that is, a time in the future), ARMBCRC bypasses the entry and issues an informational message. When you recover to a user-specified timestamp, BMC AMI Recovery Manager generates multiple steps, as follows: The ARMBTSI program inserts the timestamp into the BMC AMI Recovery Manager coordinated disaster recovery (CRRDRPT) table. The ARMBCRC program converts this timestamp into a valid RBA or LRSN. If data sharing, multiple ARMBCRC steps are generated and are synchronized to begin after the ARMBTSI step completes. The ARMBLOG program issues an -ARCHIVE LOG command. If data sharing, this step is synchronized to begin after all ARMBCRC steps have completed. Important For data sharing systems, you can choose to convert the timestamps for all members of the data sharing system in a single job, which simplifies scheduling and monitoring the timestamp conversion process. Otherwise, BMC AMI Recovery Manager generates a separate job for each data sharing member. Each job runs on the LPAR on which the member resides.
   Last recovery point registered in the Coordinated Disaster recovery table (CRRDRPT)	Uses the most recent timestamp in the CRRDRPT table This option generates multiple steps, as follows: The ARMBCRC program converts the timestamp into a valid RBA. If data sharing, multiple ARMBCRC steps are generated. The ARMBLOG program issues an -ARCHIVE LOG command. If data sharing, this step is synchronized to begin after all ARMBCRC steps have completed. Important You must have previously used the ARMBTSI program to place a timestamp in this table (see ARMBTSI—Time stamp insertion).