We have two production VM systems, plus a few others - small DR system, 2nd level test system, 1st level LPAR test system.
I always build *one*, and then copy the required parts to other systems. For those things that need to be generated differently, I have local PPF overrides/CNTL files that do the different builds, but all from the same work system.(This is pretty much limited to ACI routines - with/without VM:Secure). Shimon On 8 Jun 2006 at 7:55, Phil Tully wrote: > Alan Altmark wrote: > > >On Wednesday, 06/07/2006 at 11:07 EST, Alan Ackerman > ><[EMAIL PROTECTED]> wrote: > > > > > >>That's good news. Perhaps it is time to re-examine our staunch > >> > >> > >opposition > > > > > >>to PUT2PROD. > >> > >>Another problem with PUT2PROD that comes to mind is that we don't want > >> > >> > >to > > > > > >>install VM on every system, we want to install it once (actually twice > >>because of VPARS and VTAPE) and then copy it to all the other systems. > >> > >> > >Can > > > > > >>PUT2PROD do that now that it no longer insists on forcing off userids? > >> > >> > > > >Don't put the burden of multi-system maintenence on PUT2PROD's shoulders. > >You might be able to bend PUT2PROD to your will, but the design of the > >entire installation/service process is, as you imply, for a single system. > > > >I think people do things as you describe in order to avoid repetition and > >save time, both excellent goals. We're looking at ways to reach them and > >we're more than happy to hear how (and why!) people maintain their systems > >the way they do. > > > >Alan Altmark > >z/VM Development > >IBM Endicott > > > > > > > Having come from a site with 3+ vm systems I can assure you we installed > and maintained once and distributed the updates to other systems. > Another on this list (JIM S.) can provide the detail since he has been > handling that process for a number of years. As Marcy points out the > "other" stuff such as CA, Velocity etc has their own issues. > > Phil > Phil
