> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Mark Jacobs > Sent: Thursday, April 19, 2007 2:13 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Catalog Question > > > Is the repro mergecat process disruptive to the source > catalog? Does the > answer change if the source catalog is the system master catalog/ > > Our master catalog was defined with the imbed/replication > options and we are > looking at the best way to migrate to a new catalog without > the attributes. > > It is a six member sysplex and we would really not want to > have a sysplex > outage for the catalog switch. IPLing one at a time over a > period of time > would be fine however. > -- > > Mark Jacobs > Time Customer Service > Tampa, FL
Yes, REPRO MERGECAT is disruptive in that it REMOVES entries from the old catalog while ADDING them to the new catalog. If this is your current master catalog and it is shared, it might be possible to simply create a new master catalog (with a different name, of course). You can then: 1) IMPORT CONNECT all your current user catalogs 2) DEFINE ALIAS for all the current aliases 3) DEFINE NVSAM for all the non VSAM dataset datasets 4) DEFINE CLUSTER RECATALOG for all VSAM datasets which start with SYS1 (only works with SYS1) 5) DEFINE PAGESPACE RECATALOG for all pagespaces (regardless of the name, this will work) Steps 4 and 5 are allowed by special code in catalog processing. If you have VSAM datasets in your master catalog which do not start with SYS1, you cannot do step 4 to catalog them. 6) Update or create a new LOADxx member to point to the new master catalog. 7) Rolling IPL to use the new master catalog. NOTE - I have not done this. What I have done is use this method when I needed to create a new master catalog. But I've never done it in a sysplex environment. We only have a single z/OS image. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- 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
