Re: Anybody using a multi-sysres concept for maintenance?
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
Re: Anybody using a multi-sysres concept for maintenance?
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
Re: Anybody using a multi-sysres concept for maintenance?
On Feb 8, 2008 11:00 PM, Tobias Doerkes <[EMAIL PROTECTED]> wrote: > 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 ... I believe most of the z/VM maintenance can be done in SFS. Or otherwise you could copy the contents of the production disks (including the parm disks) into (versioned) SFS directories. You then make the SFS file pool available on all other systems (via ISFC or via IPGATE) so that you only need the few last steps to be repeated on each system. You could run MAINT disconnected on the other systems, accepting commands from MAINT on your maintenance system (again, via TCP/IP or ISFC). Rob PS Obviously some of your requirements could be challenged as well (e.g. why 20 similar z/VM images, why no shared DASD, etc). Relaxing on those gives some more attractive options. -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
Re: Anybody using a multi-sysres concept for maintenance?
Tobias,
I should also mention that from time to time PTFs will be applied that
include updates to NLS (National Language Support) files (DCSS's,
actually). So there can be more to CP maintenance than just moving CPLOAD
modules around.
Best regards,
Mark
Tobias Doerkes
<[EMAIL PROTECTED]
.COM> To
Sent by: The IBM IBMVM@LISTSERV.UARK.EDU
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
Re: Anybody using a multi-sysres concept for maintenance?
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 IBMVM@LISTSERV.UARK.EDU
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
Re: Anybody using a multi-sysres concept for maintenance?
first of all, many thanks for the response. i think maintaining a sysres like richard does, is quite a good idea. jus t 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
Re: Anybody using a multi-sysres concept for maintenance?
I maintain a production sysres that is not a part of the maintenance system. This disk does not have to be replaced when the release or version of VM changes. It has the Parm disk, the object directory, the checkpoint and warm start areas on it. When I am ready to put a new CP in production, I simply rename the current CPLOAD MODULE that in on the PARM disk, calling it CPOLD, and copy the new module to the disk. It is always a good idea to keep the old nucleus, changing its name but retaining the filetype MODULE. That makes fallback easy, you simply IPL the previous nucleus. Regards, Richard Schuh > -Original Message- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Tobias Doerkes > Sent: Thursday, February 07, 2008 6:31 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Anybody using a multi-sysres concept for maintenance? > > hi list, > > is there anybody out there using a multi-sysres-concept for > activating maintenance? we are a mvs shop. so i would like to > adopt some processes f= or maintaining vm. normally we build > up a sysres in our maintenance environment. after some > testing we deploy this sysres to all systems/sysplexes and > bring it up by ipling the image. parameters, ckpt, = etc are > separated from the sysres. > > i would like to share my thoughts and code to perform this > process automa= ted. > > regards, > > tobias. >
Re: Anybody using a multi-sysres concept for maintenance?
Tobias,
I store multiple (5-6) versions of CPLOAD MODULE on the parm disk (MAINT
CF1). Names are in the format "CPyymmdd MODULE", where "yymmdd" is
typically the date the module was generated. After application of
maintenance, I copy the new CPLOAD MODULE (found on MAINT 493/193) to CF1
with the new name, then run an EXEC I wrote called NEWCPNUC, which builds a
SALIPL command and runs it. When the operator IPL's the Standalone Program
Loader, they see a screen like this:
STAND ALONE PROGRAM LOADER: z/VM VERSION 5 RELEASE 3.0
DEVICE NUMBER: 0260 MINIDISK OFFSET: EXTENT: 1
MODULE NAME: CP071030 LOAD ORIGIN: 1000
IPL
PARAMETERS
---COMMENTS---
If problems, use backout module CP070911.
Module CP070911 was loaded from minidisk on volume V1SRES at cylinder 241.
Parm disk number 1 is on volume V1SRES, cylinders 241 through 340.
--
9= FILELIST 10= LOAD 11= TOGGLE EXTENT/OFFSET
Note that you should have more than one parm disk (CF2, CF3, ...), living
on more than one volume (just in case).
If interested, I can share the NEWCPNUC EXEC code.
Mark L. Wheeler
IT Infrastructure, 3M Center B224-4N-20, St Paul MN 55144
Tel: (651) 733-4355, Fax: (651) 736-7689
mlwheeler at mmm.com
--
"I have this theory that if one person can go out of their way to show
compassion then it will start a chain reaction of the same. People will
never know how far a little kindness can go." Rachel Joy Scott
Tobias Doerkes
<[EMAIL PROTECTED]
.COM> To
Sent by: The IBM IBMVM@LISTSERV.UARK.EDU
z/VM Operating cc
System
<[EMAIL PROTECTED] Subject
ARK.EDU> Anybody using a multi-sysres
concept for maintenance?
02/07/2008 08:31
AM
Please respond to
The IBM z/VM
Operating System
<[EMAIL PROTECTED]
ARK.EDU>
hi list,
is there anybody out there using a multi-sysres-concept for activating
maintenance? we are a mvs shop. so i would like to adopt some processes for
maintaining vm. normally we build up a sysres in our maintenance
environment. after some testing we deploy this sysres to all
systems/sysplexes and bring it up by ipling the image. parameters, ckpt,
etc
are separated from the sysres.
i would like to share my thoughts and code to perform this process
automated.
regards,
tobias.
Re: Anybody using a multi-sysres concept for maintenance?
That is one way to do it. The way I do it is to make a copy of the VM system on alternate disks. IPL that VM as guest of the running VM (second level). Apply the maintenance to the second level VM and test it. When it is working I then shut down VM and IPL from alternate disks (first level). If problems happen you can shut VM down and IPL from the old disks. Tobias Doerkes wrote: hi list, is there anybody out there using a multi-sysres-concept for activating maintenance? we are a mvs shop. so i would like to adopt some processes f or maintaining vm. normally we build up a sysres in our maintenance environment. after some testing we deploy this sysres to all systems/sysplexes and bring it up by ipling the image. parameters, ckpt, etc are separated from the sysres. i would like to share my thoughts and code to perform this process automa ted. regards, tobias. -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: Anybody using a multi-sysres concept for maintenance?
No. Since what usually changes is the CPLOAD MODULE, we just rename it to FALLBACK MODULE and place a new CPLOAD MODULE on the PARM disks. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Tobias Doerkes Sent: Thursday, February 07, 2008 9:31 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Anybody using a multi-sysres concept for maintenance? hi list, is there anybody out there using a multi-sysres-concept for activating maintenance? we are a mvs shop. so i would like to adopt some processes for maintaining vm. normally we build up a sysres in our maintenance environment. after some testing we deploy this sysres to all systems/sysplexes and bring it up by ipling the image. parameters, ckpt, etc are separated from the sysres. i would like to share my thoughts and code to perform this process automated. regards, tobias. This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Anybody using a multi-sysres concept for maintenance?
hi list, is there anybody out there using a multi-sysres-concept for activating maintenance? we are a mvs shop. so i would like to adopt some processes f or maintaining vm. normally we build up a sysres in our maintenance environment. after some testing we deploy this sysres to all systems/sysplexes and bring it up by ipling the image. parameters, ckpt, etc are separated from the sysres. i would like to share my thoughts and code to perform this process automa ted. regards, tobias.
