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 TCPIP.ETC.PROTO TCPIP.ETC.RPC TCPIP.ETC.SERVICES TCPIP.FTP.DATA TCPIP.HOSTS.ADDRINFO TCPIP.HOSTS.LOCAL TCPIP.HOSTS.SITEINFO TCPIP.MIBDESC.DATA TCPIP.SMTPNJE.HOSTINFO TCPIP.STANDARD.TCPCHBIN TCPIP.STANDARD.TCPHGBIN TCPIP.STANDARD.TCPKJBIN TCPIP.STANDARD.TCPSCBIN TCPIP.STANDARD.TCPXLBIN TCPIP.TCPIP.DATA TCPIP.TELNET.TCPXLBIN 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. Thanks for your help. Its been a long time since I've done the System Upgrade option and the details are fuzzy. JoAnn ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
