Thanks David that makes sense, and that's what I'm leaning towards. I had to make some concessions with some products, I was forced to create a symlink on the sysplex root because of how the users accessed some ISV products, so my symlink to a system specific filesystem for example '/web' links to /$SYSTEM/local/web so it removed this issues I'm was having with /usr/lpp (that was the old mount point) So, if I understand correctly you create a symlink for an ISV filesystem pointing to /$SYSTEM/usr/lpp ?
something like ln -s /$SYSTEM/usr/lpp/RTCHIN /RTCHIN this would help if this works correctly... It's been hard to convince the team to allow me to remove the system specific filesystem that are identical and create one PLEX wide filesystem mounted @ /&SYSPLEX/usr/lpp I think that would help greatly. my current structure..... rwxrwxrwx 1 CPV8281 OMVSGRP 20 Mar 11 21:02 abinitio -> /SYSA/local/a binitio rwxrwxrwx 1 CPV8281 OMVSGRP 12 Sep 26 08:20 bin -> $VERSION/bin rwxrwxrwx 1 CPV8281 OMVSGRP 9 Nov 14 10:33 cai -> /SYST/cai rwxrwxrwx 1 CPV8281 OMVSGRP 12 Sep 26 08:20 dev -> $SYSNAME/dev rwxrwxrwx 1 CPV8281 OMVSGRP 12 Sep 26 08:20 etc -> $SYSNAME/etc rwxrwxrwx 1 CPV8281 OMVSGRP 21 Mar 11 10:42 ftp -> /PLEX1/usr/local/ tp/ rwxrwxrwx 1 CPV8281 OMVSGRP 12 Sep 26 08:20 lib -> $VERSION/lib rwxrwxrwx 1 CPV8281 OMVSGRP 21 Mar 13 07:58 nfs -> /PLEX1/usr/local/ fs/ rwxrwxrwx 1 CPV8281 OMVSGRP 12 Sep 26 08:20 opt -> $VERSION/opt rwxrwxrwx 1 CPV8281 OMVSGRP 16 Sep 26 08:20 samples -> $VERSION/samp es rwxrwxrwx 1 CPV8281 OMVSGRP 12 Sep 26 08:20 tmp -> $SYSNAME/tmp r-xr-xr-x 1664 CPV8281 TTY 0 Mar 16 08:53 u rwxrwxrwx 1 CPV8281 OMVSGRP 12 Sep 26 08:20 usr -> $VERSION/usr rwxrwxrwx 1 CPV8281 OMVSGRP 12 Sep 26 08:20 var -> $SYSNAME/var rwxrwxrwx 1 CPV8281 OMVSGRP 15 Mar 11 06:57 web -> /SYSA/local/web SYSA:CPV8281:/ > let me know if I'm understanding you correcly thanks for your help Carmen Vitullo ----- Original Message ----- From: "David Jousma" <[email protected]> To: [email protected] Sent: Friday, March 16, 2018 8:51:36 AM Subject: Re: how do you handle shared ZFS in a sysplex Yea, it gets a little complicated for the non-sysres stuff. We are shared ZFS across the sysplex. We do have a couple of one-off's in /usr/lpp/ as well. So, a couple of observations I made. You have two types of filesystems. 1) those that are shared across the sysplex, 2) those that are "system/environment" specific. We have SYSRES ZFS shared as part of $VERSION for all systems running on the same SYSRES, we also do a similar process for ISV ZFS, using system symbol. For stuff that wants to be in the shared space, like /usr/lpp but really isn’t a part of that, I use symbolic links in /usr/lpp to resolve to a location outside of that filesystem. In my case it's to a directory location that resides in a system specific filesystem. It could just as easily be in some other shared part of the directory tree however. TEC1:$ ls -al total 640 drwxr-xr-x 40 P0SJR OMVSGRP 8192 Oct 25 14:52 . drwxr-xr-x 10 P0SJR OMVSGRP 8192 Oct 25 14:51 .. drwxr-xr-x 9 P0SJR OMVSGRP 8192 Jan 4 10:13 IBM drwxr-xr-x 3 P0SJR OMVSGRP 8192 Apr 27 2017 NFS drwxr-xr-x 11 P0SJR OMVSGRP 8192 Dec 15 08:22 Printsrv drwxr-xr-x 3 P0SJR OMVSGRP 8192 Oct 20 17:34 TWS lrwxrwxrwx 1 P0SJR OMVSGRP 13 Oct 25 14:52 aqt -> /opt/fitb/aqt drwxr-xr-x 7 P0SJR OMVSGRP 8192 Oct 25 15:31 bcp drwxr-xr-x 8 P0SJR OMVSGRP 8192 Apr 27 2017 booksrv drwxr-xr-x 9 P0SJR OMVSGRP 8192 Apr 27 2017 cbclib lrwxrwxrwx 1 P0SJR OMVSGRP 16 Oct 25 14:52 cicsts -> /opt/fitb/cicsts drwxr-xr-x 6 P0SJR OMVSGRP 8192 Nov 13 2015 cobol I hope this helps. Feel free to contact me off-list if you want to compare notes. We've been in shared ZFS for a few years now, and while a lot of things to think of in the beginning, its been very easy to handle going forward. _________________________________________________________________ Dave Jousma Manager Mainframe Engineering, Assistant Vice President [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Carmen Vitullo Sent: Friday, March 16, 2018 8:38 AM To: [email protected] Subject: how do you handle shared ZFS in a sysplex **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I finally was able to migrate all HFS's to ZFS's, then design a shared ZFS environment with a sysplex root, version root and system(s) root. to facilitate this environment I IPL'd each LPAR from the same SYSRES and shared parmlib using symbols for system specific parms. What I'm wondering, is we have some products that are mounted @ /usr/lpp/, this of course is resolved to $VERSION/usr/lpp, someone had installed a product there and had 3 different filesystem mounts, one for each system, it works OK, until I had to IPL one system from a different sysres, the filesystem from the other 2 systems mounted @ /usr/lpp were unmounted and the new version file system was mounted from the system I IPL'd. because of this fact, batch processing that needed that filesystem on the OTHER systems failed looking for the original $VERSION/usr/lpp. maybe not such a clear explanation but I'm wondering what other do in this case. I forced the team to move any file systems that need to be shared to /&SYSPLEX/..... and products filesystems that need to be system specific mounted @ /$SYSTEM/..... but I'm having an issue moving forward, and I think I'm going to have a problem when I migrate maint around the plex with a new sysres, will I? Any help would be greatly appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
