How can I confirm and prove that logging in CA Datacom is turned on and working?
We are using Logging for Auditing purposes.
Release : 15.1
Component : CA DATACOM/DB
The CA Datacom logging system stores log records in the LXX which are then spilled to the RXX.
Logging is always on as it is used to perform transaction backout, it can't be turned off.
However, it is only useful for recovery or for auditing purposes if LOGRCV is either YES or NO which causes the LXX records to be spilled to the RXX. If LOGRCV=NEVER, no RXX files are created so recovery is not possible.
Logging must also be turned on for each table. Only tables with LOGGING=YES will be logged to the LXX.
For audit purposes reports can be obtained from the RXX by running DBUTLTY with:
REPORT AREA=RXX.
To check the LOGRCV setting look for the following message in the MUF startup:
DB01900I - LOGRCV NO
It should be NO or YES.
This information can also be obtained by running DBUTLTY with:
REPORT AREA=LXX
Look for :
MASTER LIST RCV OPTION - NO
You can also confirm that records are being written to the LXX in the following MUF shutdown report:
MUF EOJ LOG STATUS INFORMATION
MUF EOJ, LOG CLOSED, CLEAN EOJ
LOG RECORD BYTES-2,762,412 WRITTEN-6,004,185
LOG CONTROL BYTES-57,344 ROLLBACK-0
LOG RECORD SEQ-4,591 LOG BLOCK SEQ-2,450
To check if your application tables have Logging turned on run DBUTLTY with:
REPORT AREA=CXX, DBID=nnnn
Each table should have:
LOGGING - YES
See the CA Datacom documentation in TechDocs sections Using Logging, LOGRCV, Log Area (LXX) Report and Recovery File (RXX) Report