Simplify verification of occurence/operation status after performing a CP REFRESH (dialog option 9.5) by having an available copy of the pre-refresh files on a separate controller

Currently it is very difficult to get all the occurrences and operations in the current plan (CP) into the correct status after it is necessary to perform a REFRESH of the long term plan (which deletes the current plan). In fact it is so difficult that in many cases hours or days are spent trying to avoid the need to do a CP REFRESH.  However if some preparation is done (similar to what is done for disaster recovery testing or for using the remote hot standby feature) a complete copy of all the files allocated to the affected controller can be copied to another "test" controller which is pre-defined for this purpose, and this controller can be started with job submission turned off, so that the status of any occurrence or operation belonging to an occurrence can be verififed against the ACTUAL controller after the CP has been refreshed.   If some software  to "snap" a copy of the files of the controller and restore it to a different LPAR is available, this provides  a very fast way to have a copy of all the files.  If not, a DFDSS (PGM=ADRSSU) backup and restore of the files can be done (restoring of course to a differently named set of files )- this will take some minutes but is much faster than trying to screen print the status of everything in the current plan or run various reports and WAPL jobs to get a picture of the current plan status BEFORE the refresh is done.   The key is to set this up proactively, and test it, so that in the event of the need for a CP REFRESH that "copy" of the current controller files can be generated very quickly .