Most of the execs that IBM distributes (xxxMKDIR, etc) allow you to prefix the install path with a higher level directory name. We use /maint/ so that the actual directory that these products point to is /maint/usr/lpp/<product name>. We then mount an HFS at that point to receive the maintenance. As far as implementing the new version of an existing product, we have a symbolic link in /usr/lpp/ called product that points to a directory on the root called product (/usr/lpp/product -> /product. The product directory has subdirectories for each product and each subdirectory has version identifiers (/product/db2/v8 /product/db2/v7) at each of these subdirectories we mount the correct version of the product. When someone wants to use the product they point their startup scripts or configuration files to point to the correct directory. It sounds complex but it has saved us a ton of problems and allows us to mount the version root directory as read only which can prevent folks from inadvertantly (or not) overlaying our running system code. If you have access to the SHARE archives there are several presentations on this subject (one of them mine from the Nashville SHARE). Good luck! Jon
Jon L. Veilleux [EMAIL PROTECTED] (860) 636-2683 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Patrick O'Keefe Sent: Thursday, August 03, 2006 1:43 PM To: [email protected] Subject: HFS files for IBM program products IBM program products apparently have packaging rules for Unix libraries stating that the path to these libraries will be /usr/lpp/<product_name>/. How do shops handle this when they install program products (like PrintServe, DB2, NetView, etc.) in other than their main MVS SMP zones. In particular, how do shops handle maintenance or new releases when both old and new copies of the products needs to be executed simultaneously? Symbolic links so that /usr/lpp/<product_name>/ can point into different HFSs? Temporary installation into something other than /usr/lpp/<product_name>/? Some other technique? That 2nd technique was sometimes used at my last shop, but apparently some products use hard-coded paths /usr/lpp/<product_name>/.../. Is that common, standard practice in MVS program products? To have the paths to Unix libraries hard-coded and not overridable by installations? I probably asked a question similar to this about a year ago, but couldn't find it in the archive. Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ----------------------------------------- This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
