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
