Don’t know if you have LPARs designated at TEST, DEV and PROD, but another 
variation is to incorporate the use of system symbols.   You could have a 
/shared/TECH/tools /shared/DEV/tools, and /shared/prod/tools, and instead of 
the ln -s /shared/tools /usr/local, you could use ln -s 
'$SYSSYMA/shared/&ENV./tools' /usr/tools   assuming you have a system symbol 
defined like &ENV=TECH, or &ENV=DEV , or &ENV=PROD

Then your mount statements would be

MOUNT    FILESYSTEM('USER.&ENV..TOOLS')
         TYPE(ZFS)                                       
         MODE(read) UNMOUNT                              
         MOUNTPOINT('/shared/&ENV./tools')  

This would allow you to have a version of your TOOLS filesystem by environment. 
 A USER.TECH.TOOLS, USER.DEV.TOOLS, and USER.PROD.TOOLS so that you are not 
affecting all environments at once with a change to USER.TOOLS.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Cal McCracken
Sent: Wednesday, January 08, 2014 10:51 AM
To: [email protected]
Subject: Re: Sysplex File System Sharing with Mountpoints Containing Symlinks

Thanks for your response, David. 

USER.TOOLS is not part of the z/OS-maintained file system. It's something we 
maintain internally.

I do have my VERSION values set as you noted.
 
Replacing sub-directory 'local' with a symlink looks like it will work for us. 
Thank you!
 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

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

Reply via email to