Mark Jacobs wrote:
Thanks for the pointer. I looked at the manual and it seems like it says
I can do a repro nomergecat. Change the master catalog option in
iplparm, ipl and go.
We can manage any updates in the master catalog(s) until all systems are
reipled.
Do you read it the same way I do?
Mark Jacobs
Be very careful. According to the manual, I see this:
After a REPRO of one catalog to another, the VVRs are changed to point
to the target catalog, and all subsequent processing must be done under
the target catalog.
Attention: Performing REPRO on a catalog while data sets are
open in the source catalog might result in a loss of information if any
of those data
sets extend, or other catalog updates are made. The changes
might not be copied to the target catalog, resulting in a mismatch
between the
information contained in the VVDS and the new target BCS. This
might cause the data sets to be inaccessible or receive errors.
We did a REPRO mergecat for a new MASTER in prep for a z/OS 1.7
upgrade. The client instituted a freeze for several months, so we
didn't get to IPL with tbe new MASTER.
HSM's CDS data sets were in the master catalog. When a quarterly REORG
was ran for HSM, the job failed after the deletion of the CDS indicating
wrong catalog in the VVR (or whatever it was). We had to define new
CDSs to recover. Not pretty. Any VSAM in the master will have this
problem.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
