DFS3795I IOT EEQE PURGE FAILED. AREA=areaname RBA=xxxxxxxx RC=yy
Explanation
During I/O toleration EEQE purge processing, at
least one EEQE could not be purged. For each EEQE that is not purged, IMS issues
this message followed by message DFS0488I. areaname identifies
the name of the associated area; xxxxxxxx identifies
the RBA of the associated CI. Reason code yy has
the following meanings.
- Code (dec)
- Meaning
- 04
- The request to get the CI lock failed.
- 08
- The request to get the area lock failed.
- 12
- The area OPEN request failed.
- 16
- I/O error occurred while attempted to purge the EEQE.
- 20
- I/O toleration purge was preparing to write tolerated data for a VSO area, but an area data set was stopped (or in the process of being stopped) due to a write error on the second CI. The area data set stop can cause the entire area to stop; in this case, if purge continues it can abend.
System action
IMS continues processing, but skips the EEQE purge.
Operator response
Issue the /UNLOCK SYSTEM command later to purge the EEQEs.
If the return code is 12, issue the /START AREA or UPDATE AREA START(ACCESS) command for the named areas; then issue the /UNLOCK SYSTEM again.
IMS issues return code 16 only if XRF takeover processing has not completed when you request the EEQE purge. If you reenter the /UNLOCK command after the takeover processing is complete, the purge is usually successful. To display any EEQEs that were not purged, enter the /DIS DB ALL BKERR.
If the area is stopped, recover the area.