Tobias,
Assuming you're only concerned about CP (ignoring CMS, TCPIP, etc), apply
and test your new CPyymmdd MODULE (my convention) on your test system, then
FTP it around to your 19 other systems, copy to your parm disk (MAINT CF1),
and you're all set. Even easier, set your UFTD servers and you can SENDFILE
the new module instead of FTP'ing ("SENDFILE CPyymmdd MODULE TO
[EMAIL PROTECTED] (UFTSYNC NETDATA").
Assuming you may want to service CMS, TCPIP, etc, from time to time, you
may just want to bite the bullet and have a seperate, complete installation
on each system. I just applied an armload of CP PTFs on eight different
systems earlier this week in a little over an hour, so it's not a
monumental task.
Best regards,
Mark
Tobias Doerkes
<[EMAIL PROTECTED]
.COM> To
Sent by: The IBM [email protected]
z/VM Operating cc
System
<[EMAIL PROTECTED] Subject
ARK.EDU> Re: Anybody using a multi-sysres
concept for maintenance?
02/08/2008 04:00
PM
Please respond to
The IBM z/VM
Operating System
<[EMAIL PROTECTED]
ARK.EDU>
first of all, many thanks for the response.
i think maintaining a sysres like richard does, is quite a good idea. just
to tell you why i asked this question: i need a procedure to maintain up 20
z/VMs images. moreover there is no shared dasd environment. so i have to
deliver the new maintenance via file transfer and perform the necessary
changes to make it ready for ipl automatically, because manual change for
20
images are no fun ...
regards,
tobias
