I always user SERVICE and PUT2PROD, but I use them on the 2nd lvl test
system. They don't come near the systems that real people, i.e. users,
use. As far as an ESM goes, I have RACF, so that's a moot point for me.
I realize that VM development has limited resources and I recognize that
VM installation/maintenance has to be designed or tailored for the least
common denominator that being, for example, the MVS sysprog or the UNIX
sysadmin who has been told to bring up VM in order to host LINUX.
Nevertheless I don't think that Endicott needs to go out of their way to
cut out the few remaining, experienced VM sysprogs that still haven't
retired to a rocking chair on the front porch of a retirement home.
Jim
Alan Altmark wrote:
On Tuesday, 07/15/2008 at 04:39 EDT, Kris Buelens <[EMAIL PROTECTED]>
wrote:
I work like Jim: never PUT2PROD.
Copy the runtime minidisks from the install user (eg 5VMTCP30) to
alternate addresses of the "active" user (eg TCPMAINT). When the time
is right, the mdisk addresses are swapped. This process is first
tested on the SW Installation system and then repeated on production
systems. The minidisks passwords tell which is which.
<cough> For those without ESMs, those passwords must serve a Higher
Authority.
This way we always have a backout and operators can be explained which
minidisk addresses to swap and which servers to restart in case a
backout is required.
Looking down the road, I see a rough ride for people who don't use SERVICE
and PUT2PROD.
For TCP/IP, consider using test servers with TCPMAINT 491/492. For CMS
tests, IPL 490 and use 493. Obviously you need a 2nd level system to
verify CP service.
Alan Altmark
z/VM Development
IBM Endicott
--
Jim Bohnsack
Cornell University
(607) 255-1760
[EMAIL PROTECTED]
