Re: z/os omvs maintenance service and hfs/zfs
On Wed, 1 Jul 2009 11:22:16 -0400, Klein, Kenneth wrote: >Thanks, good advice. It's working now. What is this "automount >management" all about? I picked off some good info from this thread, too. Lots of smart people here. As for automount, take a look at z/OS Unix System Servies Planning (watch the wrap): http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BPXZB291/6.0? SHELF=BPXZSH91&DT=20090112094853 With proper automount policies and directory-to-filesystem naming conventions, the system will mount the correct filesystems on the correct mountpoints (in this case, from the SMP/E DDDEFs), and you can set a timeout to have them automatically unmounted after set time on inactivity. Closest thing to foolproof I've used, though many others on this list seem to manage fine without it, too. Regards, Art Gutowski Ford Motor Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
Thanks, good advice. It's working now. What is this "automount management" all about? Ken Klein Sr. Systems Programmer Kentucky Farm Bureau Insurance - Louisville kenneth.kl...@kyfb.com 502-495-5000 x7011 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Arthur Gutowski Sent: Wednesday, July 01, 2009 10:38 AM To: IBM-MAIN@bama.ua.edu Subject: Re: z/os omvs maintenance service and hfs/zfs On Tue, 30 Jun 2009 10:16:37 -0400, Klein, Kenneth wrote: >So now if I IPL onto the new target res pack and all the files get >mounted under /Service, the apply (check) should find everything? >Should I set up the bpxprm__ to mount all these /Service mountpoints at >IPL or would it be better to mount them with the mount command? Yes, given that your DDDEFs are set up for /Service/RESZS1, an apply in the target zone pointing to RESZS1 will find the right paths. Review your APPLY CHECK allocation report to verify, before moving to APPLY. Since your follow-up note suggests you want to be able to apply maintenance to this zone from a different LPAR, then eventually be able to IPL from the SYSRES & HFS, I would discourage using BPXPRMxx to mount them at IPL. Adding mount/unmount to your clone/maintenance process would be better, and IMHO, automount management would be better still. Either way, you still have to be exceedingly careful if you go outside the sysplex (GRS) boundary (unless you have MIM). Regards, Art Gutowski Ford Motor Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
Danke vielmals. All good advice and the apply check ran showing me what all will get "touched". Ken Klein Sr. Systems Programmer Kentucky Farm Bureau Insurance - Louisville kenneth.kl...@kyfb.com 502-495-5000 x7011 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Walter Marguccio Sent: Wednesday, July 01, 2009 9:21 AM To: IBM-MAIN@bama.ua.edu Subject: Re: z/os omvs maintenance service and hfs/zfs - Original Message From: "Klein, Kenneth" kenneth.kl...@kyfb.com > I thought I would be running the apply on the system I was upgrading. You *can* apply maintenance on a live system, but this is something you can do on a sandbox LPAR, certainly not on a production LPAR. And, even if you apply PTFs on a live sandbox LPAR, this practice is not recommendable. > How can you apply maintenance to omvs _and_ z/os from a different lpar?? AFAIK, this is the safest way to apply PTFs on a z/OS system; that is, from one LPAR to a 'dead' LPAR. The DDDEFs for datasets of the target (or dead) LPAR must point to the correct SYSRES volume. The DDDEFs for PATHs of the target (or dead) LPAR must be prefixed by something like '/service/' . Then, the zFS or HFS datasets of the target LPARs must be mounted on the /service/ mountpoint on the living LPAR where the apply job run. I believe this is a normal practice, which doesn't imply any risks. Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
On Tue, 30 Jun 2009 10:16:37 -0400, Klein, Kenneth wrote: >So now if I IPL onto the new target res pack and all the files get >mounted under /Service, the apply (check) should find everything? Should >I set up the bpxprm__ to mount all these /Service mountpoints at IPL or >would it be better to mount them with the mount command? Yes, given that your DDDEFs are set up for /Service/RESZS1, an apply in the target zone pointing to RESZS1 will find the right paths. Review your APPLY CHECK allocation report to verify, before moving to APPLY. Since your follow-up note suggests you want to be able to apply maintenance to this zone from a different LPAR, then eventually be able to IPL from the SYSRES & HFS, I would discourage using BPXPRMxx to mount them at IPL. Adding mount/unmount to your clone/maintenance process would be better, and IMHO, automount management would be better still. Either way, you still have to be exceedingly careful if you go outside the sysplex (GRS) boundary (unless you have MIM). Regards, Art Gutowski Ford Motor Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
- Original Message From: "Klein, Kenneth" kenneth.kl...@kyfb.com > I thought I would be running the apply on the system I was upgrading. You *can* apply maintenance on a live system, but this is something you can do on a sandbox LPAR, certainly not on a production LPAR. And, even if you apply PTFs on a live sandbox LPAR, this practice is not recommendable. > How can you apply maintenance to omvs _and_ z/os from a different lpar?? AFAIK, this is the safest way to apply PTFs on a z/OS system; that is, from one LPAR to a 'dead' LPAR. The DDDEFs for datasets of the target (or dead) LPAR must point to the correct SYSRES volume. The DDDEFs for PATHs of the target (or dead) LPAR must be prefixed by something like '/service/' . Then, the zFS or HFS datasets of the target LPARs must be mounted on the /service/ mountpoint on the living LPAR where the apply job run. I believe this is a normal practice, which doesn't imply any risks. Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
What still confuses me about the way these jobs were set up to apply maintenance to z/os is that the bpxprm__ uses the &sysr1 symbol as the second level qualifier of the omvs.root/etc/var/java*/sigyroot/scsdroot files so if I clone to reszs3 I still have to apply my maintenance from say reszs1 to apply it to the reszs3 omvs datasets. But then the smp apply job running on reszs1 would have to set boundary to the target zone of reszs3. I thought I would be running the apply on the system I was upgrading. How can you apply maintenance to omvs _and_ z/os from a different lpar?? Ken Klein Sr. Systems Programmer Kentucky Farm Bureau Insurance - Louisville kenneth.kl...@kyfb.com 502-495-5000 x7011 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Klein, Kenneth Sent: Tuesday, June 30, 2009 10:17 AM To: IBM-MAIN@bama.ua.edu Subject: Re: z/os omvs maintenance service and hfs/zfs I have something like this: # pwd /Service # du . 16 ./RESZS1/etc 16 ./RESZS1/jv390 160 ./RESZS1/root 16 ./RESZS1/var 224 ./RESZS1 240 . # The dddefs are all set up with cloned paths just like on our production system, about 160 paths to omvs files under /Service/&sysr1. So now if I IPL onto the new target res pack and all the files get mounted under /Service, the apply (check) should find everything? Should I set up the bpxprm__ to mount all these /Service mountpoints at IPL or would it be better to mount them with the mount command? Ken Klein Sr. Systems Programmer Kentucky Farm Bureau Insurance - Louisville kenneth.kl...@kyfb.com 502-495-5000 x7011 -Original Message- From: Lizette Koehler [mailto:stars...@mindspring.com] Sent: Friday, June 26, 2009 10:54 AM To: Klein, Kenneth Subject: Re: z/os omvs maintenance service and hfs/zfs Since this is long, I thought I would take it off list. When I installed z/OS V1.9 I kept everything in the SERVERPAC (Tlibs, Dlibs, etc) as is. Then I copied the OMVS and TLIBS to SYSRES Volumes to IPL. That way I could always use the base SMP/E environment I setup for the initial install of the operating system There is a phiolosphy in the Manuals that you create new SYSRES and OMVS envrionment, and point the new OMVS environment to the /SERVICE directory. This way you can apply your maint to the new targets and not affect your production stuff. Since zFS files MUST be cataloged, you probably want to use something like OMVS.LPARname.ROOT.SYRESvol to keep them unique (OMVS.LPAR1.ROOT.SRES1A) The path you take will be however you want to maintain your systems. I prefer to keep everything in SMP/E as shipped (I use ZOS19T for tlibs and ZOS19D for dlibs and ZOS19 for all other datasets). Then I just use FDR to pick up the ZOS19T and place them on the new SYSRES home and change ZOS19T to SYS1. Then do any other customization needed for the IPL (like the SAD program) If you have questions feel free to write. Lizette -Original Message- >From: "Klein, Kenneth" >Sent: Jun 26, 2009 10:08 AM >To: IBM-MAIN@bama.ua.edu >Subject: z/os omvs maintenance service and hfs/zfs > >Newbie question: I'm starting my research into how to apply maintenance >to omvs for the first time in _my_ career. I'm fine with z/os, smp/e, >the csi and zones, put's, rsu's and so on but this shop (I'm new here) >has some clone-jobs that set up the whole hfs file structure under a >/Service node. What the heck is that for? > > >Ken Klein >Sr. Systems Programmer >Kentucky Farm Bureau Insurance - Louisville > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
I have something like this: # pwd /Service # du . 16 ./RESZS1/etc 16 ./RESZS1/jv390 160 ./RESZS1/root 16 ./RESZS1/var 224 ./RESZS1 240 . # The dddefs are all set up with cloned paths just like on our production system, about 160 paths to omvs files under /Service/&sysr1. So now if I IPL onto the new target res pack and all the files get mounted under /Service, the apply (check) should find everything? Should I set up the bpxprm__ to mount all these /Service mountpoints at IPL or would it be better to mount them with the mount command? Ken Klein Sr. Systems Programmer Kentucky Farm Bureau Insurance - Louisville kenneth.kl...@kyfb.com 502-495-5000 x7011 -Original Message- From: Lizette Koehler [mailto:stars...@mindspring.com] Sent: Friday, June 26, 2009 10:54 AM To: Klein, Kenneth Subject: Re: z/os omvs maintenance service and hfs/zfs Since this is long, I thought I would take it off list. When I installed z/OS V1.9 I kept everything in the SERVERPAC (Tlibs, Dlibs, etc) as is. Then I copied the OMVS and TLIBS to SYSRES Volumes to IPL. That way I could always use the base SMP/E environment I setup for the initial install of the operating system There is a phiolosphy in the Manuals that you create new SYSRES and OMVS envrionment, and point the new OMVS environment to the /SERVICE directory. This way you can apply your maint to the new targets and not affect your production stuff. Since zFS files MUST be cataloged, you probably want to use something like OMVS.LPARname.ROOT.SYRESvol to keep them unique (OMVS.LPAR1.ROOT.SRES1A) The path you take will be however you want to maintain your systems. I prefer to keep everything in SMP/E as shipped (I use ZOS19T for tlibs and ZOS19D for dlibs and ZOS19 for all other datasets). Then I just use FDR to pick up the ZOS19T and place them on the new SYSRES home and change ZOS19T to SYS1. Then do any other customization needed for the IPL (like the SAD program) If you have questions feel free to write. Lizette -Original Message- >From: "Klein, Kenneth" >Sent: Jun 26, 2009 10:08 AM >To: IBM-MAIN@bama.ua.edu >Subject: z/os omvs maintenance service and hfs/zfs > >Newbie question: I'm starting my research into how to apply maintenance >to omvs for the first time in _my_ career. I'm fine with z/os, smp/e, >the csi and zones, put's, rsu's and so on but this shop (I'm new here) >has some clone-jobs that set up the whole hfs file structure under a >/Service node. What the heck is that for? > > >Ken Klein >Sr. Systems Programmer >Kentucky Farm Bureau Insurance - Louisville > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
On Fri, 26 Jun 2009 11:34:02 -0400, Jakubek, Jan wrote: >We use /service/&SYSR1 like mount point/s for SMPE work... Additionally, we use automount policies to ensure the right "service" HFS' are mounted for each corresponding SMP/E zone and target SYSRES (we have LOTS). Regards, Art Gutowski Ford Motor Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
<< John McKown So, you'd first MOUNT your alternate ROOT filesystem dataset on the /Service subdirectory. You'd then mount your alternate VAR filesystem at /Service/var, XML at /Service/usr/lpp/ixm, SHPUROOT at /Service/usr/lpp/ported, SHPHROOT at /Service/usr/lpp/php, SHPEROOT at /Service/usr/lpp/perl, MQS at /Service/usr/lpp/mqm, and so on. >>> We use /service/&SYSR1 like mount point/s for SMPE work... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
In addition make sure your SMPE dddef's point to /service/. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of McKown, John Sent: Friday, June 26, 2009 10:30 AM To: IBM-MAIN@bama.ua.edu Subject: Re: z/os omvs maintenance service and hfs/zfs > -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Klein, Kenneth > Sent: Friday, June 26, 2009 9:08 AM > To: IBM-MAIN@bama.ua.edu > Subject: z/os omvs maintenance service and hfs/zfs > > Newbie question: I'm starting my research into how to apply > maintenance > to omvs for the first time in _my_ career. I'm fine with z/os, smp/e, > the csi and zones, put's, rsu's and so on but this shop (I'm new here) > has some clone-jobs that set up the whole hfs file structure under a > /Service node. What the heck is that for? > > > Ken Klein Updating the running system is "frowned upon". The way that I do maintenance is to put the maintenance onto an alternate set of OS volumes. That is easy to do with "legacy" datasets. However, to update z/UNIX files, the container dataset must be "mounted" on the updating system. So, the /Service subdirectory is where you mount your alternate z/UNIX filesystems. Think of it as a similar to the SSA alias used in SMP/E to refer to the datasets on your alternate RES volumes via that normal catalog. So, you'd first MOUNT your alternate ROOT filesystem dataset on the /Service subdirectory. You'd then mount your alternate VAR filesystem at /Service/var, XML at /Service/usr/lpp/ixm, SHPUROOT at /Service/usr/lpp/ported, SHPHROOT at /Service/usr/lpp/php, SHPEROOT at /Service/usr/lpp/perl, MQS at /Service/usr/lpp/mqm, and so on. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Klein, Kenneth > Sent: Friday, June 26, 2009 9:08 AM > To: IBM-MAIN@bama.ua.edu > Subject: z/os omvs maintenance service and hfs/zfs > > Newbie question: I'm starting my research into how to apply > maintenance > to omvs for the first time in _my_ career. I'm fine with z/os, smp/e, > the csi and zones, put's, rsu's and so on but this shop (I'm new here) > has some clone-jobs that set up the whole hfs file structure under a > /Service node. What the heck is that for? > > > Ken Klein Updating the running system is "frowned upon". The way that I do maintenance is to put the maintenance onto an alternate set of OS volumes. That is easy to do with "legacy" datasets. However, to update z/UNIX files, the container dataset must be "mounted" on the updating system. So, the /Service subdirectory is where you mount your alternate z/UNIX filesystems. Think of it as a similar to the SSA alias used in SMP/E to refer to the datasets on your alternate RES volumes via that normal catalog. So, you'd first MOUNT your alternate ROOT filesystem dataset on the /Service subdirectory. You'd then mount your alternate VAR filesystem at /Service/var, XML at /Service/usr/lpp/ixm, SHPUROOT at /Service/usr/lpp/ported, SHPHROOT at /Service/usr/lpp/php, SHPEROOT at /Service/usr/lpp/perl, MQS at /Service/usr/lpp/mqm, and so on. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: z/os omvs maintenance service and hfs/zfs
/Service node. What the heck is that for? Unless you want to apply maint to your running OMVS components, then pointing to the /Service (or whatever) directory will some 'issues'. Generically you run the maint from a driving system and /Service (and mounting) lets you point to the target's OMVS. Jack Kelly 202-502-2390 (Office) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
