On Mon, 19 May 2008 15:17:12 -0500, McKown, John <[EMAIL PROTECTED]> wrote:
>Is there a good tutorial on how to migrate from a SYSPLEX(NO) to >SYSPLEX(YES) root file system? At present, although I am in a basic >sysplex, I have separate root filesystems. I had to get the system split >quickly and without sufficient planning and research. > >/tmp is in a separate filesystem >/dev is in a TFS filesystem >/var is in a separate filesystem >/etc is in a separate filesystem > The z/OS UNIX System Services Planning manual has all the information you need. That is all I used. But you may have to read in-between the lines a little for some stuff. Here are my notes from when I did it, which should save you some time. ========================================== See the chapter on "Shared HFS in a sysplex" from the planning manual. Also see this on the web for animated view: http://www.ibm.com/servers/eserver/zseries/zos/bkserv/animations/ussanims.html There are 4 data sets required (3 new ones - create using samples): 1) Sysplex root - SYS1.SAMPLIB(BPXISYSR) 2) System specific HFS - SYS1.SAMPLIB(BPXISYSS) 3) Version HFS (old unix root) 4) Couple data set - SYS1.SAMPLIB(BPXISCDS) ** Version HFS ("old" OMVS ROOT) needs &SYSR1/2/3 name in it Automount delay: /etc/auto.map.u Make sure it is not 0 in a shared environment. Change to 10. Policy must be the same... so userid.HFS not userid.sysname.hfs since only one can be mounted at /u/userid. If not the same, last system IPLed in the share group wins. PARMLIB changes: COUPLExx: Add DATA TYPE(BPXMCDS) and new PCOUPLE/ACOUPLE data sets. BPXPRMxx: Move all FILESYSTYPE and MOUNT statements to a shared BPXPRMxx member. This includes things like NFS as they must be activated on all systems in the sysplex sharing group - even if not used. (AO consideration during implementation) Add: SYSPLEX(YES) VERSION('&SYSR1.') Mount for sysplex root - read/write and AUTOMOVE Mount for system specific HFS - read/write & UNMOUNT ** LOCAL MOUNTPOINTs previously in OMVS root need to be created in sysplex root. For example, /products. Change: MOUNTPOINT('/$VERSION') for old root - should be AUTOMOVE MOUNTPOINT('/&SYSNAME./???') for system specfic HFS and data sets like /etc, /var, /dev, /tmp MOUNTPOINT('/&SYSNAME./usr/lpp/Tivoli') + AUTOMOVE AUTOMOVE is the default for MOUNT. UNMOUNT should be specified for system specfic HFS data sets like /etc, /dev, /tmp, /var (and filesystems mounted below those directory levels). Automation changes: IPL/SHUTDOWN Example: Due to having to have all FILESYSTYPE defined on all systems, things like NFS will be started on all systems. Make sure F OMVS,SHUTDOWN is used and not BPXSTOP! Or at least F BPXOINIT,SHUTDOWN=FILESYS Other considerations / changes: Version HFS ("old" OMVS ROOT) needs &SYSR1/2/3 name in it MOUNTPOINTs previously in OMVS root need to be created in sysplex root. Need to resolve /products conflicts to have a single /products. Migrate cron to /etc - see Unix System Services Planning (also see below for cron) Anything under /usr must be migrated out or changed to symlink like cron so it is mounted somewhere else or have a "version" copy (on the sysres set) like the omvs root and tivoli hfs. (see below for /usr/local) ==================================================================== CRON: (see Unix System Services Planning) Directory /etc/spool and /etc/cron need to be created (755). Delete all files /dirs under /usr/spool and /usr/lib/cron from new root HFS... so if mounted at servz14: rm -fr /servz14/usr/spool rm -fr /servz14/usr/lib/cron Create a symbolic link for /usr/spool that points to /etc/spool and /usr/lib/cron from new root HFS... so if mounted at servz14: ln -s /etc/spool /servz14/usr/spool ln -s /etc/cron /servz14/usr/lib/cron ==================================================================== usr/local Directory /etc/local needs to be created (755) Create a symbolic link for /usr/local that points to /etc/local .. so if mounted at servz14: (directory /etc/local should already exist for systems using this) rm -fr /servz14/usr/local ln -s /etc/local /servz14/usr/local HTH, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
