Re: Sysplex Maintenance and USS

[Bruce Hewson]

Symlinks are you friend.

Mount your product files to /$VERSION/usr/lpp/ etc

the symlink ./usr/lpp/xxx  to the required version mounted filesystem

Hope that gives you pointers

Regards
Bruce

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Sysplex Maintenance and USS

[Barbara Nitz]

>So, how does one rollout maintenance in a sysplex one system at a time without 
>disrupting the ability to access these products?

The way I do it for the links that weren't totally screwed up when I started 
here:
at /usr/lpp I mount a 'links'-ZFS, i.e. /usr/lpp/java gets an 
OMVS. ZFS mounted. The actual Java-versions are then mounted 
'inside' that LINKS-ZFS. For version changes of Java all I need to do is 
unmount the old one, set a new mount point for the new version and off I go. 
For refresh of an existing Java version, I put in a new  LINKS ZFS since 
I normally refresh Java together with z/OS when  changes anyway. Any 
other ZFS name (different from the old one) would do it, too, but then I need 
to remember to update BPXPRMxx.

So the 'trick' is not to mount to usr/lpp directly but instead mount another 
ZFS at the appropriate usr/lpp mount point and mount the product off from there.

Regards, Barbara

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Sysplex Maintenance and USS

[Chris Parker]

Our USS file system tends to follow the one recommended in the USS Planning 
Guide.  When we bring up a system in our sysplex with new maintenance, the 
VERSION root is mounted with all its related file systems.  What I noticed 
today though, is that our product related file systems, which are mounted off 
directories in  '/usr/lpp', now need to be prefixed with the old VERSION root 
directory in order to be accessed from the updated system because they are 
still mounted to /usr/lpp in the old VERSION root for the other members in the 
sysplex.  All of these products install into /usr/lpp.  The USS Planning Guide 
recommends using /usr/lpp.  So, how does one rollout maintenance in a sysplex 
one system at a time without disrupting the ability to access these products?  
I'm assuming there is a trick that I am not finding in the documentation.  The 
only think I can think of is to change the directory location to something that 
hangs off of the sysplex root filesystem since these are not maintained during 
the z/OS maintenance process.

Thanks in advance,
Chris
---
NOTICE:
This email and all attachments are confidential, may be proprietary, and may be 
privileged or otherwise protected from disclosure. They are intended solely for 
the individual or entity to whom the email is addressed. However, mistakes 
sometimes happen in addressing emails. If you believe that you are not an 
intended recipient, please stop reading immediately. Do not copy, forward, or 
rely on the contents in any way. Notify the sender and/or Imperva, Inc. by 
telephone at +1 (650) 832-6006 and then delete or destroy any copy of this 
email and its attachments. The sender reserves and asserts all rights to 
confidentiality, as well as any privileges that may apply. Any disclosure, 
copying, distribution or action taken or omitted to be taken by an unintended 
recipient in reliance on this message is prohibited and may be unlawful.
Please consider the environment before printing this email.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN