All, (warning, long post)
Getting ready to take the plunge and implement Unix Shared filesystems with SYSPLEX Root, etc. Part of this effort is going to have to include some file system "cleanup". We have the typical Serverpac supplied SYSRES filesystems, no problem there. But we also have a collection of "stuff" that has been added over the years, like ISV file systems, extra versions of JAVA no longer supplied by serverpac, HOME directories for TECH support staff, local filesystems for whatever, etc. What I am looking for is some documentation or "industry standards" - if there are any, on what the recommended placement in the directory structure is. I'm also looking for some examples of others implementation of SYSPLEX Root? The Chapter 7 of the FM is a short 30 pages, and lacks enough real world examples. Like I said, I'm good with the IBM supplied filesystems related to the SYSRES. That's a no brainer. It's our add-on stuff I need to deal with. For Example, today's setup: /u - mostly home directories for the few users that we have in Unix, but has also been a scratch pad for SMPE work space. Does not currently have a automount policy. Ultimately, want this automount controlled, and in the SYSPLEX root as IBM suggests, so that Unix uses truly have ONE home filesystem, regardless of which system they are on. /opt/(something) - we are currently using this for non-serverpac supplied copies of JAVA, and other software TOMCAT, JSPWIKI, etc. Would still like local copies per system of these file systems, but /opt gets mapped to $VERSION in the SYSPLEX root, not to the System specific due to the IBM supplied symbolic links. /usr/opt - file system created, mounted, but empty. Same issue with regards to where it gets mounted. Would still like local copies per system of these file systems, but /usr gets mapped to $VERSION in the SYSPLEX root, not to the System specific due to the IBM supplied symbolic links. /usr/local - file system created, mounted, but empty. Same issue with regards to where it gets mounted. Would still like local copies per system of these file systems, but /usr gets mapped to $VERSION in the SYSPLEX root, not to the System specific due to the IBM supplied symbolic links. With SYSPLEX Root, and filesharing, the new root looks like: # cd / # ls -al total 12 lrwxrwxrwx 1 E008058 OMVSGRP 9 May 23 07:34 $SYSNAME -> $SYSNAME/ lrwxrwxrwx 1 E008058 OMVSGRP 9 May 23 07:34 $VERSION -> $VERSION/ drwxr-xr-x 6 E008058 OMVSGRP 768 May 23 07:37 . drwxr-xr-x 6 E008058 OMVSGRP 768 May 23 07:37 .. drwxr-xr-x 2 E008058 OMVSGRP 256 May 23 07:34 ... -rw------- 1 E008058 OMVSGRP 0 May 23 07:37 .sh_history drwxr-xr-x 18 E008058 OMVSGRP 896 Jul 24 2012 RSTT2A drwxr-xr-x 6 E008058 OMVSGRP 544 May 23 07:33 TEC5 lrwxrwxrwx 1 E008058 OMVSGRP 12 May 23 07:34 bin -> $VERSION/bin lrwxrwxrwx 1 E008058 OMVSGRP 12 May 23 07:34 dev -> $SYSNAME/dev lrwxrwxrwx 1 E008058 OMVSGRP 12 May 23 07:34 etc -> $SYSNAME/etc lrwxrwxrwx 1 E008058 OMVSGRP 12 May 23 07:34 lib -> $VERSION/lib lrwxrwxrwx 1 E008058 OMVSGRP 12 May 23 07:34 opt -> $VERSION/opt lrwxrwxrwx 1 E008058 OMVSGRP 16 May 23 07:34 samples -> $VERSION/samples lrwxrwxrwx 1 E008058 OMVSGRP 12 May 23 07:34 tmp -> $SYSNAME/tmp drwxr-xr-x 5 E008058 OMVSGRP 704 May 23 08:00 u lrwxrwxrwx 1 E008058 OMVSGRP 12 May 23 07:34 usr -> $VERSION/usr lrwxrwxrwx 1 E008058 OMVSGRP 12 May 23 07:34 var -> $SYSNAME/var So, systems, I truly want local to that system now need to be mounted to $SYSNAME/....(something), but NOT /usr/(something), or /opt/(something) since that gets a symbolic link back to the $VERSION (which) is the old ROOT filesystem before doing sysplex sharing. Would it be as simple as adding extra symbolic links to the root file system? Something like: Usr/local -> $SYSNAME/usr/local Usr/opt -> $SYSNAME/usr/opt _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
