I did some maintenance on PERFKIT and PUT2PROD it on my production system. The process rebuilt CMS. This was a major surprise, although it was my fault for not figuring out what PUT2PROD was going to do before it did it (read the build list). I think the default action of PUT2PROD should be to indicate what exactly it's going to do with options to skip various steps in the process to protect the novice (and also the lazy) systems programmer, and also those with "different" procedures, for example VSSI customers.
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Wednesday, July 16, 2008 11:36 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Question on how RSU maintenance is being handled with DIRMAINT and RACF in the picture On Wednesday, 07/16/2008 at 09:39 EDT, Rob van der Heij <[EMAIL PROTECTED]> wrote: > On Wed, Jul 16, 2008 at 6:05 AM, Alan Altmark <[EMAIL PROTECTED]> wrote: > > > BTW, there's nothing wrong with building a test system and then copying > > that into production in whatever way you wish. I'm not going to dictate > > to anyone how to get your system into Final Real Production. > > So we're not going to see new messages like: "z/VM installed new > service and will need to shutdown reipl. Do you want that right now or > do you want to lose your work in 5 minutes while you're on the > phone..." ;-) No. You'll also have the opportunity to delay the nag message for 3 minutes or 14.5 hours (your choice). The messages will go to the system operator, but in a way that is not visible to system automation. ;-) Alan Altmark z/VM Development IBM Endicott
