Tom, The requirements we have for applying maintenance to the z/OS operating system here has dictated how we name the HFS 'service' mountpoint. The 'key' requirement I must adhere to is: Must be able to apply any maintenance to any of the z/OS operating system levels we have installed using any z/OS image.
I chose to create multiple SYSRES volumes for each z/OS operating system level we maintain. For example, we currently run z/OS R4 on our seven z/OS images. We have four SYSRES volumes ( named: ASR41Z, ASR42Z, ASR43Z & ASR44Z ) that support these seven z/OS images. Each z/OS R4 SYSRES volume may have a different 'maintenance level' applied to it. Our preference is to apply our z/OS maintenance to these SYSRES volumes in numeric order, sometimes that is not possible. So, we addressed this requirement by taking the '/service' concept one level further. We created a second-level directory to the '/service' directory and added that second-level directory to the HFS DDDEFs within each Target Zone. For example: ASR41Z /service/ASR41Z/ ASR42Z /service/ASR42Z/ ASR43Z /service/ASR43Z/ ASR44Z /service/ASR44Z/ The above structure allows me another way to cross check the DDDEFs in a Target Zone are referencing the correct HFS ( assuming I mounted the correct HFS dataset to the correct mountpoint I listed above ). I ensure that by having HFS mount and unmount steps in each SMP/E Apply Check & Apply jobs that are executed. That ensures no HFS was left mounted from a previous job and that no HFS is left mounted after a maintenance run. HTH Glenn Miller --------------------------------------------------------------------------- This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. ABN AMRO Bank N.V. (including its group companies) shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. ABN AMRO Bank N.V. (or its group companies) does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. --------------------------------------------------------------------------- ---------------------------------------------------------------------- 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
