When I maintained multiple systems I used one master system to do all the maintenance on. On the master system there was a custom CNTRL file for
each system, master or not, which included an AUX file line unique to tha t system (as well as a common AUX file for all systems). This allowed control over which custom mod's any system would get during assembly or build. (Very useful back in the days of DMKRIO, SYS, and SNT). Upgrading non-master systems was a simple matter of copying the productio n disks & CP nucleus from the master to the non-master. To aid doing t his at remote systems I wrote a "Bulk File Transfer Receiver" system to send files through the RSCS network and receive them onto disks at the remote system. (For local systems, disk-to-disk or via tape worked fine.) Putting service it into production on any system was a standard process o f resaving saved systems, swapping mdisk addresses, & an IPL. Brian Nielsen On Wed, 7 Jun 2006 23:24:10 -0500, Marcy Cortes <[EMAIL PROTECTED]> wrote: >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
