Ever since 1.4 we have used a single 3390-9 that contains everything we need to migrate from sysplex to sysplex. It still fits comfortably as of 1.7. Some clarifications:
The OMVS HFS files do not live on this sysres. What does live there is a DFDSS unload backup copy of the HFS files. After copying the sysres volume to another sysplex for migration, we run a DFDSS job to reload the HFS files, which are multivolume and take as much space as needed. The sysres itself does not contain everything supplied by ServerPac, only what's needed to IPL and run a system. For example, no DLIBs on the sysres. SHASPSRC is also excluded because it's large and is not needed except were we do maintenance. All non-sysres data sets associated with ServerPac are kept on two other 3390-9 volumes, so three 3390-9 volumes altogether for ServerPac. The CSI and supporting SMP/E datasets live off the sysres and are never migrated. One key to maintaining our sanity is the use of aliases set up by ServerPac--a scheme we keep for the entire life of the release. For example, 'OSR17.SYS1.LINKLIB' points to the SYS1.LINKLIB on R17RES, while 'OSR14.SYS1.LINKLIB' points to the SYS1.LINKLIB on R14RES. My take on the questions: 1. The HFS files are somewhat bigger for 1.7: 38000 vs. 31000 tracks in 1.4. With multivolume allocations, we hardly notice the difference. Other data sets are fairly similar in size to previous releases. There is some growth, but nothing that would make us restructure the volume layouts. 2. We have strenuously avoided a multi-volume sysres. That takes a bit of manipulation up front in the ServerPac dialog, but we feel it's worth some time in order to simplify life later on. 3. HFS files are associated with the sysres by name, not by location, so it doesn't matter where they live. Each sysplex has a set of volumes that SMS reserves for system HFS with HLQ 'OMVS'. This volume set is pretty stable across releases. 4. Components are kept together according to what's installed in the MVST100 target zone. That always starts with ServerPac and will include any updates or additions that come before the next ServerPac. CICS and DB2 are maintained by other folks into other CSI's and live somewhere off of sysres. Likewise for ISV products from STK/Sun, etc. . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] IBM Mainframe Discussion List <[email protected]> wrote on 01/20/2006 06:21:03 AM: > We are currently preparing to migrate from z/OS 1.4 to 1.7. We would > appreciate feedback on the following based > upon your experiences. Have a great weekend. > > 01. Is 1.7 significantly larger then 1.4 that we should consider going > to a multi IPL pack system? > 02. Is a multi IPL pack system a good idea anyway? (we use mod 9s) > 03. Do you move your root file system to a separate volume? > 04. Do you segregate all the IBM additional software from the operating > system itself: base elements and opt features? > > Please feel free to share your maintenance philosophy. We are looking > for improvements as to how we currently > handle things. Thank you! ---------------------------------------------------------------------- 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
