I have a very large OS/390 customer running Remote Copy over Fibre.
When using Synchronous Remote Copy, DR-Simulation by pulling Fibre cable off then using DB2 RECOVER on Remote Site works ok, all DBs and tablespaces are fine, restart is RC=0.
I was working with IBM France some 20 years ago and "understand" merely names in DB2.
I do not know what/how their DB2 RECOVERY is set-up.
In that regards, I would like to know "what" should I be asking them to supply me to check if their DRP for a DR-site with Asynchronous Remote Copy is healthy or not.
But when they do the same test with Asynchronous Remote Copy, and attempt the same thing, sometimes it works, sometimes it does not and they get error message MSGDSNI02I "Page Logically Broken".
It was as if, either, DB2 Logging did not keep some consistency, or, for DB2 RECOVER for Asynchronous re-start, there was some additional set-up the customer should do when collecting logs to allow pointing to a proper, 100% consistent, synch-point or check-point...
Basically, I would like to know (sort of "Monkey-see, Monkey-do") if there is a "Best-Practice" DSNZPARM setup for Synchronous Remote Copy DR Recovery-Restart, and a "Best-Practice" DSNZPARM setup for Asynchronous Remote Copy DR Recovery-Restart?
Meaning: Sample Setup for Logging on main-site that would allow a smooth fine DR-site Recovery for sites "copied" using Asynchronous Remote Copy.