ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

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

Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services Datacom/AD CA ecoMeter Server Component FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA On Demand Portal CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET 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.