RECOVERY OPTION=BACKWARD Does not support multiple RECJOB options.

book

Article ID: 35303

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

Problem

When running CA Datacom/DB DBUTLTY to perform a RECOVERY OPTION=BACKWARD, multiple RECJOB options beyond the first one are ignored.

A typical usage might be:

//SYSIN    DD  *
  RECJOB JOBNAME=MYJOB01,RUNUNIT=13579
  RECJOB JOBNAME=MYNEXT02,RUNUNIT=14826
  RECJOB JOBNAME=ANOTHER1,RUNUNIT=14380
  RECOVERY OPTION=BACKWARD,MISMATCH=IGNORE
/*

Environment: 

This applies to CA Datacom/DB or CA Datacom/AD Version 14.0 only.

Resolution/Workaround:

This problem is corrected with a solution: RO79964 (DB 14.0 #455), "INCOMPLETE BACKWARD RECOVERY WITH MULTIPLE RECJOB CARDS"

In addition, this problem can occur if the RECJOB cards have the JOBNAME not in ascending order and one or more of the RECJOB cards has other options than JOBNAME. Therefore, to run this successfully before the solution can be implemented, you can either run the job with only a single RECJOB option, or you can ensure the RECJOB options are ordered by ascending JOBNAME.

Additional Information:

For more information about the Backward Recovery process, please refer to the CA Datacom/DB DBUTLTY Reference Guide, in the section, “RECOVERY (Rebuild a Database).”

As always, please contact CA Technologies support for CA Datacom if you have further questions.

Environment

Release:
Component: DB