MVSFORUMS.com

rtman99 · Beginner Joined: 25 Mar 2003 Posts: 2 Topics: 1

i am trying to clone a system to new volumes and want to "zap" the master catalog entries for volsers to my new system. i need a routine to read/update the catalog/
i want to scan for volser and replace inside the catalog.

taltyman · Posted: Tue Mar 25, 2003 5:09 pm Post subject:

We do this all the time without having to mess with the catalog. Look into using system variables as the volume entry for the catalog. Can give you more detail when I get back to work tomorrow but you can have the catalog use ******, etc plus you can roll your own. We roll a set of 3 res volumes and never have to worry about the catalog or duplicate volsers.

taltyman · Posted: Thu Mar 27, 2003 9:24 am Post subject:

This link will get you started. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2E220/2.7?SHELF=IEA2BK21&DT=20020116153755

Again we can IPL off of any of our res volumes without any catalog changes by simply changing the load address. The initial setup was not without gotchas but it's doable.

Here is a sample of our IEASYM00 member in SYS1.IPLPARM. Note that &SYSR1 is automatically set to the volser of the IPL volume.
SYSDEF LPARNAME(SYST)
SYSCLONE(TT)
SYMDEF(&SUBAREA.='16')
SYMDEF(&VTAMPRM.='TT')
SYMDEF(&MVSNAME.='SYST')
SYMDEF(&MVSID.='T')
SYMDEF(&HSMPARM.='TY')
SYMDEF(&LOGCLS.='0')
SYMDEF(&RSUVAL.='00')
SYMDEF(&SYSR2.='&SYSR1(1:4).R2')
SYMDEF(&SYSR3.='&SYSR1(1:4).R3')

Here is a sample of a catalog entry for a dataset on one of our cloned volumes.
NONVSAM ------- SYS1.APL2.SAP2FNTL
IN-CAT --- CATALOG.MASTER.SYST
HISTORY
DATASET-OWNER----TSTUSER CREATION--------2002.078
RELEASE----------------2 EXPIRATION------0000.000
VOLUMES
VOLSER------------&SYSR2 DEVTYPE------X'00000000'
Notice VOLSER and DEVTYPE values.

We use 3 volumes for our cloning process. 2 for the IBM datasets that are the target libraries in our mvs zone. 1 for datasets that we wish to included with the cloning process but that aren't part of the MVS zone. This 3rd volume enjoys the same catalog process so there are no catalog issues and these datasets can be unit tested with the maintenance and simply roll in/out with any maintenance we do. A sample dataset would be our linklib for exits.

rtman99 · Beginner Joined: 25 Mar 2003 Posts: 2 Topics: 1

thanks, i saw that, and it works great. i was trying to do it the hard way, i wanted to do a full pack copy and simply "zap" the volsers. the reason is the driving system has the volsers defined in it already. for the new system i would like to use indirect references. thanks for your help.. robert termini

taltyman · Posted: Fri Mar 28, 2003 12:33 pm Post subject:

If you go that way then make sure you scan proclib, parmlib, etc for volser references. On our first shot we ended up IPLing about 3 times finding all the gotchas that we missed (such as mstjcl00 and jes2). We also copied brodcast, proclib, parmlib (actually we converted to use iplparm) and even the master catalog to the same volume as the IODF is on and cataloged them there. In PROGxx we use the indirect references as well.
We name our volsers using SYpmRn as a template where p is lpar, m is maintenance id and n is 1/2/3. We roll through an X,Y,Z identifiers for maintenance. So for system B on X maintenance the volsers would be SYBXR1, SYBXR2, SYBXR3. When we start a maintenance roll we copy the volumes (clip them), smpe zone copies, do a mass edit on volsers in the zones.