Actually, the fix doesn’t change the way BESClient checks the PendingFileRenameOperations settings.
It, instead, modifies the internal logic BESClient uses to detect if the restart has been triggered by an action and to clear the related keys.
In details, when an action creates a pending restart situation, the Windows BESClient creates a global Atom, and the global Atom persists until a machine restart: it allows BESClient to detect if the machine has been restarted since the Atom was created.
Before implementing the fix for APAR IJ13194, BESClient was checking for the global Atom unless the PendingFileRenameOperations test showed no remaining items.
For this reason, it did not clear the existing restart flags in actions.
With the fix, BESClient examines the global Atom even when the PendingFileRenameOperations are present, and used the Atom information to clear the existing restart flags in actions (and preventing any further unexpected reboot).
