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
