That's exactly what I prefer. /service has its own filesystem, used purely to hold the directory entries for IBM and non-IBM directories/objects, which are all stored in their own mounted filesystems.
Ant. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Hunkeler Sent: Monday, 16 October 2017 3:25 AM To: [email protected] Subject: AW: non-ibm products in /service ? >What is the recommendation regarding having non-ibm products mounted in >/service ? When it comes to IBM SMP/E managed parts, you change the DDDEF path by prefixing it with /service. So /bin becomes /service/bin. However, I see no reason why you cannot expand on that and build some subdirectories in /service, say /service/ibm/zos, /service/ibm/db2, /service/somevendor/someproduct, etc. as mount points for the corresponding service file systems. Then adjust the DDDEFs accordingly, or for non-SMP/E products adjust the install script, install job or whatever. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
