In defense of selective RECEIVE. Maybe it's because we have several folks 'in charge' of various products; more likely it's because I'm a very disorganized person. I can't keep track of what I should or should not APPLY other than 'all'. Besides IBM's classifications, I get occasional requests from other people to install a PTF or two for the specific product they support. They're all grown-ups. I don't question whether MQ or HSM or IP really does or does not need a particular fix suggested by the respective SME. If I RECEIVE(ALL), how will I keep of what I should APPLY in the next cycle? (Rhetorical question. Suggestions not solicited.)
Since I'm not fully capable of any procedure other RECEIVing selectively and then APPLYing all, that will remain my SOP. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] "Chase, John" <[email protected] > To Sent by: IBM [email protected] Mainframe cc Discussion List <[email protected] Subject .edu> Re: RECEIVE ORDER ERROR 04/28/2009 03:36 PM Please respond to IBM Mainframe Discussion List <[email protected] .edu> > -----Original Message----- > From: IBM Mainframe Discussion List On Behalf Of Mark Zelden > > On Tue, 28 Apr 2009 13:11:43 -0700, Edward Jaffe wrote: > > >Chase, John wrote: > >>> If I did that, wouldn't I have all of the PTFs that haven't yet gone > >>> through CST? > >>> > >> > >> Yes, but you can APPLY by SOURCEID(RSU*). > >> > > > >Right now, I just RECEIVE ORDER CONTENT(RECOMMENDED), whatever comes > >back comes back, and I APPLY *all* of it with a "canned" job stream > >that's always the same. Simple. > > > >The suggestion seems to be to use RECEIVE ORDER CONTENT(ALL) and then > >selectively manage what comes back. I become the one who decides which > >fixes have undergone enough testing and which have not. I have to keep > >track of these numbered/dated RSUs to help understand which fixes I want > >and which I don't. And, I have to be sure to specify the right RSU > >value(s) at APPLY time. > > > > From where I sit, this process sounds like extra work. Clearly, this is > >a job to be undertaken by a professional sysprog--something I've never > >claimed to be. > > > > Not any extra work at all. It's just changing where the "filter" is. > > Currently you filter at the source by selecting "CONTENT(RECOMMENDED)". > If you change to "CONTENT(ALL)" and change your APPLY JCL to > "SOURCEID(RSU*)", you are applying the same service. The "PRO" is that > you would have any PTF you needed in an emergency. The "CONs" are > possibly longer download times and storing more PTFs locally. Actually, to apply *everything* you get with CONTENT(RECOMMENDED), you'd need to specify SOURCEIDs RSU*, HIPER and PRP. I've tried it already with one "batch" of CICS maintenance, using this "canned" APPLY job: APPLY FORFMID( list of CICS FMIDs ) SOURCEID( RSU* HIPER PRP ) GROUPEXTEND BYPASS( whatever's appropriate for your case ) CHECK . "Works a treat." -jc- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
