In my case, like Jerry's, I have more than one VM image feeding off of the same maintenance disks. My production PARM disks are not a part of the installation and maintenance system, so, as stated, I really do not care what goes on the CFx disks. I check for changes and update my real disks as appropriate. CF1 gets used only by a 2nd level system that insures that the base system ipls and runs following installation and maintenance activities.
Wasn't there a time when CF1 was "production", CF2 was "backup" and no CF3 existed? Perhaps back in the days when the T-shirt with the VM Bear on the diving board about to dive into the green VM/SES pool was popular. There were a few years when I had no installation and maintenance responsibility. When was CF3 added to the mix? Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark > Sent: Thursday, March 11, 2010 2:14 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CP's Parm Disks > > On Thursday, 03/11/2010 at 11:11 EST, "Schuh, Richard" > <rsc...@visa.com> > wrote: > > Not that I mind having it written on the CFx disk, I do not > use it on > any live > > system, but I seem to remember someone on this list, > someone from IBM, > saying > > that the PARM disks were there for our use in customizing > the system > > and > that > > they would not be violated by IBM. I don't remember who > said it, but I > think > > his initials were A.A. > > The CF1 disk ("production") is yours to do with as you > please. CF2 is a "build" disk and belongs to IBM. CF3 is a > copy of your CF1. You put it on the CF1 and it will end up > on CF2 and CF3. > > If PUT2PROD doesn't meet your needs, you need to tell us in > what way it interferes with your ability to service your systems. > > Alan Altmark > z/VM Development > IBM Endicott >
