Marcy and Phil, I have had concerns about IBM products always, or almost always, being designed as an initial installation ever since working on VM/IS for 9370s back in 1989.
We create a new userid identifying the operating system, (VMESA122, ZVM520, ZVM510) and do the installs there; 2nd level. There is a corresponding userid for the miscellaneous ids named 440RES, 510RES and 520RES. If I remember correctly, PUT2PROD is run one and only one time, at the end of that install. We have a policy here that forbids the DASD management folks from messing with any DASD that starts with VM and ALL VM DASD must start with VM, so the installation volume serial numbers, 510RES, 510PAG or whatever never last with that name for more than six hours. They are clipped as soon as we are finished the installation. Yes, I correct the USER DIRECT file and stuff. z/VM maintenance is then done from the ZVM510 or ZVM520 userid depending on what z/VM level we are doing. We support 5 VM systems, a mixture or 5.1.0 and 5.2.0. So the CPLOAD MODULE is copied from the 493 to whatever CF1, 2 or 3 disks for those systems. We use a CMS IPLer so we can IPL CMS20, CMS21, CMS22, CMS (whatever version is current production for us). The CMS disks are owned by $CMSLIVE. The install 490, 49D and 49E are DDRed to whatever $CMSLIVE we assign to the CMS level. The CMS DCSSes are named in conjunction with their corresponding CMS, so we have INSTSG9E, CMSPIP21, CMSFIL22, now CMSFILB2 since maintenance has been applied to SFS, etcetera. This allows us to have IPLers CMS22, CMS22TST and CMS22OLD, with the SYSTEM SEGID file pointing to the appropriate DCSSes (SVM20, INSTSG21, whatever) The default DCSS names are only on the installation system and are not on any of the five systems. Similar things with GCS, DV, REXX. LE is an animal unto itself. For VM/VTAM we use the 5654010A id. We rotate among the GCSA, GCSB and GCSC NSSes with the VTAMA, VTAMB and VTAMC DCSSes. The original idea being to map the GCS NSS with the VTAM DCSS of the same suffix. I probably should have named those VTAM DCSSes with numeric instead of alphabetic suffixes as we apply lots of VTAM maintenance. Oh Well! For TCP/IP, the minidisk ownership is transferred to 4TCPIP40, 5VMTCP10 and 5VMTCP20. Maintenance done there. Then the 491 and 492 are DDRed to an x91 and x92 until we go into production then the 59y and x9y are flip-flopped in the directory. By the way, we do not use SFS for SES/E maintenance, only minidisks. Jim S. -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Thursday, June 08, 2006 12:24 AM To: [email protected] Subject: Re: HCPSEC068E when doing PUT2PROD SAVECMS Alan wrote: "We have 5 primary VM systems and 11 (?) VM guests. Does anyone install VM separately on each of multiple systems? Does even IBM? " That's a good question. Was wondering what all of you with > 5 systems do about that. Right now we maintain them individually (it wasn't that long ago that we had 1 system). Now I'm hearing rumblings about maybe adding 2-4 more systems for capacity/availability reasons... If we go from 6 to 10, that's a lot more VM work. Not just VM, but all the other stuff.. (velocity, ca stuff..) Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------
