Is it possible for you to install Omegamon to different Target and DLIB zones? (in the same Global as z/OS)
------------------------------------------------------------------------------------------------------------------------------- *Lucas Rosalen* Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com <lrosa...@br.ibm.com>* LinkedIn: http://br.linkedin.com/in/lrosalen Phone: +48 792 809 198 2015-11-23 22:51 GMT+01:00 J O Skip Robinson <jo.skip.robin...@sce.com>: > Being able to install maintenance separately can be very important > depending on your shop's organization and the distribution of duties among > (even a small number of) folks. I see two classes of components: > > 1) Those closely akin to z/OS that install on and migrate with sysres. > 2) Those not in category 1, including products managed by other people on > their own timetable. > > I believe that it's best for category 2 products to be installed in one or > more zones outside of the common z/OS zone and even ordered separately. For > example, we tried a while back ordering Omegastuff in the common ServerPac. > But some Omegamon products here needed to be managed in concert with new > CICS or DB2 releases irrespective of z/OS level. Combining did not work and > caused problems for other folks. Once components begin cohabitating in a > single zone, handling them by different rules is complicated, > time-consuming, and error prone. Omegamon is especially unruly because of > the manual (non-SMPE) work needed for migration. We went back to ordering > and managing Omegamon separately. > > . > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > jo.skip.robin...@sce.com > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jousma, David > Sent: Monday, November 23, 2015 8:10 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):SMPE apply excluding certain FMID's? > > I've done that, and it works. I guess I should have been more clear to > Kurt's question. I actually would like to maintenance Omegamon's > separately than the rest of the Operating system. The issue is being able > to apply general maintenance to all other FMID's with the exception of > OMEGAMON at my choosing. It's not a huge issue, more of general > convenience for the folks that will have to review Omegamon hold data. > _________________________________________________________________ > Dave Jousma > Assistant Vice President, Mainframe Engineering david.jou...@53.com > 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f > 616.653.2717 > > -----Original Message----- > From: Robert A. Rosenberg [mailto:hal9...@panix.com] > Sent: Thursday, November 19, 2015 8:55 PM > To: IBM Mainframe Discussion List > Cc: Jousma, David > Subject: Re: SMPE apply excluding certain FMID's? > > At 14:35 +0000 on 11/19/2015, Jousma, David wrote about Re: SMPE apply > excluding certain FMID's?: > > >Do you really want/need to segregate applying maintenance for the > >Omegamon suite, or during a maintenance cycle do you simply want to > >more easily identify the relevant HOLDs just for >Omegamon? I don't > >necessarily have in mind a solution for you, but I'm curious what your > >real goal is. > > > >The latter. > > An APPLY CHECK listing your created Omagamon FMIDSET (or the FMIDs) will > give you this info since only Omegamon SYSMODs will be selected. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
