We also use a form of this strategy so there is NEVER a chance the running environments get impacted. Service is applied to a static environment, and then cloned as necessary to form resvol sets. All running systems us indirect cataloging and symbolics to locate datasets as needed.
Jerry Whitteridge Manager Mainframe Systems & Storage Albertsons - Safeway Inc. 925 738 9443 Corporate Tieline - 89443 If you feel in control you just aren't going fast enough. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Skip Robinson Sent: Monday, January 18, 2016 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Cloning a Sysres and ZFS Most posts in this thread seem to support the strategy of 'cloning a running system in order to do maintenance'. For as long as I can remember, we have pursued the opposite strategy: the service environment is permanent for the life of a ServerPac and is cloned to produce running systems to populate the Enterprise. DDDEFs, once defined, are never changed; hence the chance of error is near zero. There is no overlap between service and running systems. The service environment is dump/restored to create running system(s) with identifiers like sysplex and/or sysres name embedded in the restored objects. Everything is shared within a sysplex; nothing is shared across sysplex boundaries. This strategy is probably incompatible with z/OSMF managed maintenance, but we have yet to give that a go. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile jo.skip.robin...@att.net jo.skip.robin...@gmail.com > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Chambers, James > Sent: Monday, January 18, 2016 08:04 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Cloning a Sysres and ZFS > > Hi Tom, > > 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 > > Thanks > > James > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Tom Marchant > Sent: 18 January 2016 15:46 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Cloning a Sysres and ZFS > > On Mon, 18 Jan 2016 14:41:32 +0000, Chambers, James wrote: > > >Is there a better way to deal with the HFS or ZFS DDDEFs? > > Include the SYSRES VOLSER as part of the dsname. When you mount it, you > can use &SYSRES in the mount specification. > > -- > Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ________________________________ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
