Sorry to be late on this but Mike....this one is a keeper. Thanks for the bits...
--- On Fri, 3/5/10, Mike Walter <mike.wal...@hewitt.com> wrote: From: Mike Walter <mike.wal...@hewitt.com> Subject: Re: CP's Parm Disks To: IBMVM@LISTSERV.UARK.EDU Date: Friday, March 5, 2010, 10:45 AM 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). I wrote a local EXEC to keep CF1 and CF2 synched (other that SYSTEM CONFIG there are not a lot of frequent changes),. Instead of making he CF2 the regular backup, I COPY the old SYSTEM CONFIG to -1SYSTEM CONFIG (with rolling renames up to -9SYSTEM CONFIG so we can go back up to 9 changes). Same with CPLOAD MODULE as -1CPLOAD MODULE, and any other changes files although they are handled manually since there are far fewer changes to them. That local exec also automatically runs CPSYNTAX on the new SYSTEM CONFIG file before exiting, providing clear warnings if it did not end normally. Hint: you *do* faithfully run CPSYNTAX after *every* SYSTEM CONFIG file change, even 1-lines', right? If the Operator needs to back out for some reason, they are instructed to call z/VM support first. We don't want them blindly backing out an important change without involving someone who might instead take corrective action. If they need to back out a changed file, we explain how to do so by IPLing with "LOADPARM rdev" and using SALIPL to select from the various backup -nSYSTEM CONFIG or -nCPLOAD MODULEs. IBM's method of copying CF1 to CF2 (SERVICE (?) and PUT2PROD) only provides one backout layer. So far our operators have never needed to use the CF2 disk. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Lesseg, Jon" <jon.les...@pacificorp.com> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 03/05/2010 09:11 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 Bill, Thanks for clarifying this. The SERVICE and PUT2PROD is still a black box for me at this time. I'll keep my own copies of SYSTEM CONFIG pre changes also. It's nice to know there are knowledgeable folks with real world experience out there to bounce questions to. This may be just the beginning of a bunch of questions to the list as I work to get my head around this VM creature. Thanks again. Jon L -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Bill Munson Sent: Friday, March 05, 2010 5:03 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: CP's Parm Disks Jon, When you update anything on CF1 it is CURRENT for the next IPL. the parm disks CF2 and CF3 are backup disks that you can IPL from if you need to GO BACK for any reason. I would not copy anything from CF1 to CF2 or CF3 myself. When you apply SERVICE and PUT2PROD this will copy CF1 to CF2 to be used as the new back up and CF2 is copied to CF3. I believe that is the correct order anyway it is copied for you by the Service process and that is the answer to your original question. good luck Bill Munson Sr. z/VM Systems Programmer Brown Brothers Harriman & CO. 525 Washington Blvd. Jersey City, NJ 07310 201-418-7588 President - MVMUA http://www2.marist.edu/~mvmua/ VM Project Officer - SHARE http://seattle.share.org/joinme http://www.linkedin.com/in/BillMunson "Lesseg, Jon" <jon.les...@pacificorp.com> Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 03/04/2010 05:28 PM Please respond to The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject CP's Parm Disks This is probably a bonehead question, so please have patience as I?m new to VM. When I update SYSTEM CONFIG on MNTCF1 after releasing and linking and setting access, am I responsible to update the copies on MNTCF2 & MNTCF3 after I?m comfortable with the results using something like COPYFILE or is it maintained for me? Q CPD Label Userid Vdev Mode Stat Vol-ID Rdev Type StartLoc EndLoc MNTCF1 MAINT 0CF1 A R/O 520RES FF0C CKD 39 158 MNTCF2 MAINT 0CF2 B R/O 520RES FF0C CKD 159 278 MNTCF3 MAINT 0CF3 C R/O 520RES FF0C CKD 279 398 THX, Jon L. ------------------------------------------------------------------------------ This email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else, unless expressly approved by the sender or an authorized addressee, is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action omitted or taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender, delete this e-mail and destroy all copies. ============================================================================== *************************** IMPORTANT NOTE*****************************-- The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman & Co., its subsidiaries and affiliates ("BBH"). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus. ******************************************************************************** ------------------------------------------------------------------------------ This email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else, unless expressly approved by the sender or an authorized addressee, is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action omitted or taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender, delete this e-mail and destroy all copies. ============================================================================== 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.
