DFS4671I COULD NOT CLEAN UP AFTER DEDB ALTER DUE TO MISSING DATA IN LOGS. ALTER TOKEN=tttt tttt
Explanation
During IMS restart, IMS detected that the DEDB Alter utility was running when IMS abnormally terminated. Not all log records for the DEDB Alter utility run were detected, so clean up could not be performed. This situation can occur when a restart checkpoint, an XRF start checkpoint, or a FDBR start checkpoint spans the DEDB ALTER execution.
Reason codes:
- 01
- While processing the emergency restart command against DEDB ALTER, the restart checkpoint spanned the DEDB ALTER run. The data required for the /ERE command to complete DEDB ALTER was on log records that were logged before the restart checkpoint. The /ERE command was unable to find the required data.
- 02
- During Extended Recovery Facility (XRF) tracking, an internal error occurred during DEDB ALTER ADD AREA processing. The data required for XRF to complete DEDB ALTER was on log records that were logged before the restart checkpoint. XRF was unable to find the required data.
- 03
- During Fast Database Recovery (FDBR) tracking, an internal error occurred during DEDB ALTER ADD AREA processing. The data required for FDBR to complete DEDB ALTER was on log records that were logged before the restart checkpoint. FDBR was not able to find the required data.
System action
Emergency restart continues.
System programmer response
The DEDB Alter utility was not completed, so manual cleanup must be performed before the AREA can be used. Instruct USER DFSERA10 to pull all log records for this IMS with the specified token to determine which log records were processed. To determine which DEDB/AREA needs to be cleaned up before use, compare this information with the DEDB Alter utility jobs that were active when the IMS abnormally terminated.