DFS2487I UNABLE TO COMPLETE REDO DURING XRF TKO - AREA aaaaaaaa- RSN cccc

Explanation

During XRF takeover, DEDB REDO processing includes the following:
  • Refreshing the second CI for all block-level shared areas to pick up the changes from the sharing subsystem that might not have been sent to the restarting subsystem.
  • Notifying the sharing subsystem if utility or HSSP cleanup was done during takeover.
This message indicates that REDO processing was unable to perform these tasks for area aaaaaaaa. cccc identifies the reason and can be one of the following values:
ER2L
REDO was unable to obtain the lock needed.
ER2R
REDO was unable to refresh successfully the second CI.
ER2U
REDO was unable to notify successfully the sharing subsystem that utility or HSSP cleanup was done during takeover. This condition can be caused by either an I/O error or by a problem with the notify process.

At the time this message is issued, area aaaaaaaa has successfully completed all other REDO processing. The problem indicated in the message might be resolved by closing the area and allowing it to go through normal area open processing when it is next accessed. Therefore, it is not necessary to mark the area as recovery needed and, except in the case of a notify error, it is not necessary to prohibit the sharing subsystem from accessing the area.

System action

If an error occurred while notifying a sharing subsystem, the sharing subsystem is notified to stop the area. The area is closed on the restarting subsystem and message DFS3705I is issued. If the error recurs when the area is next opened, the area is stopped and marked recovery needed.

System programmer response

If REDO processing was unable to complete utility or HSSP cleanup, the area must be reopened on the restarting subsystem (or stopped, started and reopened on the sharing subsystem) before a utility or HSSP can be started for the area.

Module

DBFERS20