CISCOMMON SERVICES FOR Z/OS90S SERVICESDATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OSCOMMON PRODUCT SERVICES COMPONENTCommon ServicesDatacom/ADCA ECOMETER SERVER COMPONENT FOCEASYTRIEVE REPORT GENERATOR FOR COMMON SERVICESINFOCAI MAINTENANCEIPCUNICENTER JCLCHECK COMMON COMPONENTMainframe VM Product ManagerCHORUS SOFTWARE MANAGERCA ON DEMAND PORTALCA Service Desk Manager - Unified Self ServicePAM CLIENT FOR LINUX ON MAINFRAMEMAINFRAME CONNECTOR FOR LINUX ON MAINFRAMEGRAPHICAL MANAGEMENT INTERFACEWEB ADMINISTRATOR FOR TOP SECRETXpertwareCompress Data Compression for MVSCompress Data Compression for Fujitsu
After switching to backup CPU, I received the following errors. Even recycling ENF STC does not help to resolve this problem.
13.09.03 STC00408 *CAS9359E - Unrecoverable Database subtask failure detected. Recycle ENF 13.09.03 STC00408 *CAS9208E - CA-ENF DB: Database Insert error:72 reason:0 13.09.03 STC00408 CAS9303E - Event JOBFAIL no longer recorded due to DB error 0012
Could you please tell me what is causing the issue?
Why do I get the message: CA-ENF DB: Database Insert error:72 reason:0 after switching to backup CPU?
CA Common Services 14.1 - z/OS supported releases -
Looking at the ENF joblog, you can check if LOGRCV was set to NO in your Datacom environment, the default is LOGRCV=NEVER. So the recommendation is to go into your :
DATACOM.CUSMAC(AXDATIN1) and set it back to LOGRCV=NEVER; please check if yours is set to LOGRCV=NO.
What NEVER does is to allow the LOGFILE (LXX) to be reused and will not write anything to a Recovery File (RXX).
The LOGRCV=NO allows these records to be written periodically but only when necessary. The LXX/RXX files are used for backup and recovery. Keep in mind, however, that the ENF database is self sustaining, contains only transient data, and no backup is necessary.
So here are our recommendations:
1. Edit your DATACOM.CUSMAC(AXDATIN1) member and change the current value of LOGRCV from LOGRCV=NO to LOGRCV=NEVER.
2. Shutdown ENF and run DATACOM.R14.INSTJCL(AD14LXXI) to reinitialize the log file to use the LOGRCV value.
3. Restart ENF.
This will clear up the situation and prevent this from occurring in the future.