Richard, No need for the extra work. If you last IPLed with CPLOAD MODULE, and you put a new one on the config disk as CPLOAD MODULE, then that's the one that will be loaded. CP doesn't know about previous file dates/times, just the filename and type (and the type had BETTER be "MODULE"!).
We always rename the existing CPLOAD MODULE as: -1CPLOAD MODULE (incrementing any other -nCPLOAD MODULEs as needed, too), and place a new CPLOAD MODULE on the config disk. We place the CPLOAD MAP there (COPYFILE PACKed and renamed as well to match the MODULE), too. That way we can always back out to CPLOAD MODULE version -1, -2, -3, etc. for as many as we have room for on our config disks (size increased as one of the first steps after installation). The original distributed CPLOAD MODULE was renamed (IIRC) by PUT2PROD as 'CPLOLD MODULE', and we often keep the very last one from *before* VM:Secure was installed as something like: -CPNOVMX MODULE. There have been a few times where I walked operations through a SALIPL, picking a previous -1CPLOAD MODULE to get the system up without my having to drive in. Still got the system back up within the SLAs. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Schuh, Richard" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 11/07/2006 11:24 AM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Automatic ReIPL What John has suggested is that if I want the module loaded when the system IPLs following a crash to be different than the one last loaded, I need to use the SET IPLPARMS command to specify the new module. That was the answer to what I hoped I was asking :-) I am going to stage a new CPLOAD MODULE and schedule a SHUTDOWN REIPL MOD CPLOAD. If I use SET IPLPARMS, I can tell Operations that the scheduled IPL need not be done if there is an intervening crash and soft IPL. Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of O'Brien, Dennis L Sent: Tuesday, November 07, 2006 8:13 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Automatic ReIPL Maybe I'm misunderstanding the question, or John's answer. The behavior I've seen here is that both an automatic abend and SHUTDOWN REIPL will IPL the module that's currently named CPLOAD MODULE. I always install maintenance with SHUTDOWN REIPL, and QUERY CPLOAD verifies that I've IPLed the new module. I had one incident where I'd staged a new module, and before I could do SHUTDOWN REIPL, the system abended and auto-restarted with the new module. Of course, the fix for the abend was in the new module. Dennis There are 10 kinds of people in the world; those that understand binary and those that don't. -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of John Franciscovich Sent: Tuesday, November 07, 2006 05:54 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Automatic ReIPL True, as long as you have not used SET IPLPARMS to change IPL parameters that might cause a different version of a module with the same name to be found on another PARM disk. John Franciscovich z/VM Development >>That is correct sir. >Does the soft IPL done following an ABEND act the same when choosing a >module to load as if a SHUTDOWN REIPL (without any parameters or options) >had been entered? That is, will it choose the module that was last IPLed >rather than the one that currently has CPLOAD as its filename? > >Regards, >Richard Schuh 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.
