Question & Answer
Question
I am migrating from z/OS 1.11 to 1.13 using ServerPac. I installed the ServerPac on my test LPAR. In the ServerPac jobs, I used the CATCVTM and CATCONV jobs to merge my current Master Cat with the z/OS 1.13 ServerPac Master cat. This process has been successful and my test LPAR is running z/OS 1.13 Now, to migrate my prod LPAR, I need to merge my current prod Master Cat with the z/OS 1.13 ServerPac Master cat. However, in the document for the catalog conversion, it states . .. Run CATCVTM on one system only; do not use this job to migrate catalogs to subsequent systems. Without having to re-install all the z/OS 1.13 code to create a new, fresh ServerPac Master cat, what is the process for migrating a second Master catalog with the z/OS 1.13 ServerPac Master catalog? My 2 LPAR's share the z/OS system files/volumes, so the z/OS 1.13 prod Master cat needs to reference the z/OS system files on the same volumes for both systems.
Answer
The big question here is do you share the Master Catalog between your Test and Prod LPARs?
As you're aware the Dialogs allow you to specify one new Master Catalog for the installation and your existing master catalog. We then do a REPRO MERGECAT on a temporary copy of the old Master Catalog into the new Master Catalog, which will update the NVR and VVR records for the master catalog and connect the other user catalogs.
So, with that in mind the ServerPac process is designed for a one to one system, so a multi system deployment or cloning isn't part of the process.
A couple of questions though. Are you using the same master catalog on the Prod and Test LPARS?
Or are you using different copies of the catalog on different volumes but with the same name?
If you are sharing the master catalog, then you shouldn't need to run through the conversion. You just may need to import connect other user catalogs.
If it is a different catalog then you would need to re-configure you order, specifying a new master catalog. You can save your existing configuration and re-create the order, using the saved configuration as
a model.
You can do this by:
- save a the current configuration.
Select the current order from the 'Order List' panel (CPPP6071).
Enter 'S' on the 'Installation Options for Order' (CPPPFLOW) panel, then enter the HLQ for the data set you'll want to save to, and provide a description.
First Setup is fine. Reply 'Delete' if you see 'DELETE an EXISTING Configuration'.
- Once you see 'CPP0604006I SAVE Request SUCCESSFUL' then go back to the CPPP6071 panel and select your 1.13 order
- Enter 'C' to create the order, and then your installation method - Full System Replacement or Software Upgrade.
Select your JES and JES/SDSF options.
- You should see panel 'Create Configuration' (CPPP6011), and your saved version of the current order should be displayed. Place an 'S' beside this saved configuration, and then enter 'CR' on the command line.
- Reply Delete if you see 'DELETE an EXISTING Configuration'.
- Now reply 'MERGE' for the pop-op confirmation window.
- If the merge is successful you should see 'CPP0601004I WORK Configuration Created'.
- You can then PF3 out, and then select the remaining options, which should have been carried over from the current option. You can update the Alias screen.
Another option would be to create a Copy of the Master Catalog. There is a sample procedure in the DFSMS Managing Catalogs manual at:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2C191/2.4.
3.1?SHELF=dgt2bkb1&DT=20120124143550&CASE=
So to summarize the Dialogs only provide one master migration path. If you want to deploy this then you'd be looking at traditional method to copy the Master Catalog.
Historical Number
13824;082;000
Was this topic helpful?
Document Information
Modified date:
03 September 2021
UID
isg3T1019473