On Mon, 18 Jan 2016 16:03:39 +0000, Chambers, James <[email protected]> wrote: >We already include it like OMVS.RESPR1.ROOT but the DDDEF only has the path. >The below shows a DDDEF taken from the >apply, it still means I need to make >sure I got the mount right and the ZONEEDIT unlike the standard DDDEFs that >use the >volser to make sure the correct dataset is updated. > >DDDEF NFSCUTIL PATH '/Service/usr/lpp/NFS/IBM/ and PATHHFS OMVS.RESDD2.ROOT >
Consider something along the lines of: /Service/zos/RESDD2/usr/lpp/NFS/IBM/ in the DDDEFs. As part of your cloning process, ZONEEDIT the path names so the new path names align with the new filesystem name. Then, use UNIX automount to manage /Service/zos. Map /Service/zos/<volume> to OMVS.<volume>.ROOT. Provided the cloning process goes according to Hoyle, this will ensure consistency of maintenance between the MVS and UNIX environments. This approach was developed by another regular contributor of this list to handle a large number of target environments, but can be used in any sized shop. It is proven and reliable. Regards, Art Gutowski General Motors, LLC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
