Why can?t I find ADDIT commands executed by a Backward Recovery job on Accounting tables?

book

Article ID: 14910

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

A DBUTLTY Backward Recovery job is submitted to back-out the DELETs commands executed by a previous job. The recovery job worked fine, the deleted records are correctly re-added to the correct tables and a RXX report shows that the Backward Recovery job executed several ADDIT commands. But on Accounting tables there is no evidence of the ADDIT commands executed by this job.



Why can’t I find ADDIT commands executed by a Backward Recovery job on Accounting tables, even if the job worked fine and an RXX report shows them?

Environment

Release: DBCISF00200-15.1-Datacom-Database-Option for CICS Services
Component:

Resolution

DBUTLTY and MultiUser internal tasks sometimes use internal commands that are not documented. Backward Recovery issues an internal "add" command to reverse the DELET commands; the internal "add" command is then logged (i.e. written to the LXX and so to RXX too) as ADDIT because of recovery/restart reasons. However, as it’s not a real ADDIT, the command is not intercepted by Accounting Facility.