In the cases below (TCPIP.**, EOX.**, EOY.**) the datasets, once configured, rarely change.
To support SERVERPAC system replacement, I have placed these datasets on the SERVERPAC CATALOG volume. This volume is *never* copied to the PRODUCTION images. On the PRODUCTION images, I have copied these datasets to non-sysres, shared volumes. I have also moved EOX.**, EOY.** to a user catalog on my production images. These datasets are not necessary for IPL or operation. There are a few changes to LPALST, LNKLST,... to accommodate this change. This could also be done with the TCPIP.** datasets, but IMO, is not worth the effort, since the TCPIP.** qualifier is also used by TCPIP itself. IOW, copy these datasets (one last time) to a shared, non-sysres volume, configure, and faggadabouddit. BTW, IMO the SYSTEM UPGRADE option is a great deal of work and more prone to errors than SYSTEM REPLACEMENT. YMMV. HTH, <snip> We are contemplating switching from ServerPac Full System Replacement to the System Upgrade Option. That means we would use our existing master catalog, which is on the ServerPac "catalog" volume along with the IODF datasets, SYS1.PARMLIB, SYS1.PROCLIB, and some other operational datasets. One set of these operational datasets are the TCPIP datasets, which we recreate with every full system replacement ServerPac: TCPIP.ETC.IPNODES ..............................snippage TCPIP.TELNETSE.TCPXLBIN Do these need to be rebuilt with every z/OS upgrade? If so, how do you handle these datasets during a ServerPac SU option? Should we keep them on the "catalog" volume? They are in the master catalog and shared by 3 LPARs, while each LPAR has its own TCPIP profile dataset. Along the same lines are the EOY datasets. Do you reuse the existing catalog volume for a ServerPac System Upgrade option? SYS1.PARMLIB and SYS1.PROCLIB are on the volume, which also complicates things a bit. But if we want to use the existing master catalog and keep the master catalog, IODF's, PARMLIB, PROCLIB, ... together it seems that we will have to use the existing catalog volume. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
