Replicate save status and last save information across nodes in PowerHa Cluster. Merged

In a PowerHA cluster, if I perform a save operation (to a tape drive) in a FlashCopy system that information is not spread among other systems in cluster specially production (main) system.

This cause some objects that must be saved before delete cannot be saved in another system different than its own system, for example, Journals Receivers. It would be interesting if the "Save date/time" attribute and others related attributes of the object where replicated and/or distributed when the object is saved on a flashcopy node within the same cluster.

Use Case #1

In a PowerHA cluster we use one of the Flashcopy systems to perform tape backups. Some elements that reside in iASP, such as journal receivers, must be properly saved before being removed from production.

When these objects are saved on our flashcopy system there is nothing in production to indicate that they have already been saved. It can be skipped with DLTJRNRCV DLTOPT(*IGNINQMSG), however it is not certain that they were saved completely.

This forces having to save these elements directly in production to ensure that they have been properly backed up before they are eliminated.

Use Case #2

We have store procedures that delete some "temporary" files in production every week, these files reside in libraries in iASP and are saved in FlashCopy. It would be very helpful if some system views like QSYS2.OBJECT_STATISTICS included some information that the item was saved on another node in the same cluster.