I would like to have a copy of it.
Billy On 5 Mar 2010 at 12:23, Mike Walter wrote: > The CPCONFIG EXEC was my brainchild, the one to which I was referring in > my previous posts. It does NOT maintain IBM's SERVICE and PUT2PROD method > of using CF2 as a backup disk. You probably downloaded it from this > listserve sometime since 2005. The last update record (at the bottom in > the Epilog comments) shows: 20050523 mrw - Correct handling of "Yes" or > '1' prompt. > > I can re-post it if anyone cares. > > Mike Walter > Hewitt Associates > The opinions expressed herein are mine alone, not my employer's. > > > > > > "Frank M. Ramaekers" <framaek...@ailife.com> > > Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> > 03/05/2010 10:33 AM > Please respond to > "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> > > > > To > IBMVM@LISTSERV.UARK.EDU > cc > > Subject > Re: CP's Parm Disks > > > > > > > Somewhere (I have since tried to find the source, but have failed) I > have a CPCONFIG EXEC that automates much of the maintenance of CF1 and > CF3. It includes maintaining previous generations of SYSTEM CONFIG: > > cpconfig > > DMSVML2060I MAINT CF1 linked MR as 0CF1 file mode I > > > > The following "*SYSTEM CONFIG" files exist on the I(CF1) disk now: > > FILENAME FILETYPE FM FORMAT LRECL RECS BLOCKS DATE > TIME > -1SYSTEM CONFIG I1 F 80 271 6 2010-02-16 > 07:58:27 > -2SYSTEM CONFIG I1 F 80 271 6 2010-01-12 > 09:04:29 > -3SYSTEM CONFIG I1 F 80 270 6 2009-11-06 > 17:37:29 > -4SYSTEM CONFIG I1 F 80 270 6 2009-11-06 > 17:37:29 > -5SYSTEM CONFIG I1 F 80 261 6 2009-10-28 > 13:52:38 > -6SYSTEM CONFIG I1 F 80 246 5 2009-09-11 > 10:18:11 > -7SYSTEM CONFIG I1 F 80 246 5 2009-08-25 > 07:37:17 > -8SYSTEM CONFIG I1 F 80 240 5 2009-08-24 > 09:39:30 > -9SYSTEM CONFIG I1 F 80 239 5 2009-07-30 > 07:37:17 > SYSTEM CONFIG I1 F 80 271 6 2010-03-03 > 13:00:37 > Do you want an automatic copy/rename of them as a backup > > before starting? (Reply: Yes | 1 | No | 0 | Quit) > > > > ...when exiting: > > 10:32:59 * MSG FROM MAINT : +++ NOTE: The "SYSTEM CONFIG I" was not > changed. > DMSVML2060I MAINT CF2 linked RR as 0CF2 file mode O > > 40 identical files on both disks. > > DASD 0CF1 DETACHED > > MAINT's 0CF1 accessed in mode A. > > CF1 update complete and in production... > > ------------------------------------------------------------------------ > ------ > > > CF2 update in progress... > > DMSVML2060I MAINT CF1 linked RR as 0CF1 file mode I > > DASD 0CF2 DETACHED > > DMSVML2060I MAINT CF2 linked MR as 0CF2 file mode O > > DASD 0CF2 DETACHED > > MAINT's 0CF2 accessed in mode B. > > DASD 0CF1 DETACHED > > CF2 update complete and in production... > > ------------------------------------------------------------------------ > ------ > > Frank M. Ramaekers Jr. > > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On > Behalf Of Mike Walter > Sent: Friday, March 05, 2010 9:45 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CP's Parm Disks > > There any many ways to do this, each with their own merits. > Understanding > how SERVICE and PUT2PROD silently update the CF1 and CF2 disks is > important. > > I prefer to think of CF2 as a resource to be used only if CF1 gets > trashed > (my human, hardware, or any other error). > : > : > > _____________________________________________________ > > This message contains information which is privileged and confidential and > is solely for the use of the > > intended recipient. If you are not the intended recipient, be aware that > any review, disclosure, > > copying, distribution, or use of the contents of this message is strictly > prohibited. If you have > > received this in error, please destroy it immediately and notify us at > privacy...@ailife.com. > > > > > > > The information contained in this e-mail and any accompanying documents may > contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if this > message has been addressed to you in error, please immediately alert the > sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents of > this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure compliance > with our internal policies and to protect our business. E-mails are not > secure and cannot be guaranteed to be error free as they can be intercepted, > amended, lost or destroyed, or contain viruses. You are deemed to have > accepted these risks if you communicate with us by e-mail. >
