Maintaining 20 VM systems from a central point, using SENDFILE/remote SFS/shared disk based tools is what I did the last 10 to 15 years. I created/extended things that allow me now to create/reuse SW distribution "jobs", including saving segments, running RACF, DIRMAINT, CP, CMS commands to run before or after the installation of files. We don't need to logon on the target system to get it ready. The "jobs" can contain verification steps to avoid running it twice. As usual: documention is limited; SFS is a prereq as the jobs are stored there. The CMS/GUI interface is optional. Contact me offline and so we can see what we can do
2008/2/9, Thomas Kern <[EMAIL PROTECTED]>: > Then you might want to take a look at the PIPEDDR package on IBM > Downloads page. It has the capability of reading a DASD (Full or > Minidisk) transmitting it over tcpip to a partner system running PIPEDDR > to receive it and write it down to its DASD. After that, some midnight > execs can move things into place (CPLOAD, DCSSBKUP files, minidisks, > etc). Then just have the operators shutdown and IPL. Packing all of your > staging areas onto a single physical volume can make it simpler to > transfer rather than sending a a dozen or two. > > /Tom Kern > > > Tobias Doerkes wrote: > > 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 > > > -- Kris Buelens, IBM Belgium, VM customer support
