The only reason I considered the bypass was because the PE chain was preventing the APPLY of the PTFs to aid detecting and migrating from USERCSA.
> -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Jousma, David > Sent: Tuesday, September 17, 2019 12:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Considering Bypassing ERROR HOLD for OA58037 > > I'm getting confused by this thread. I thought I recalled you had said the > PTF > you were bypassing was for S16E? All of those DEB Check PTF's are in > support of the changes needed for OSPROTECT. And yes, we ran into the > S16E issue on certain application datasets, only in a blue moon. Eventually, > IBM got it all figured out, and the problem is fixed. I do recall they said > they > saw the problem in VPS, where VPS was opening/closing an IMAGELIB many > times. > > But none of this had anything to do with USERKEY CSA. That’s an entirely > different animal, and needs to be rectified before going V2.4. > > I suspect you won't have much luck backing these PTF's off because they > reach out and touch a lot of different modules. The only real option would > be if you have a known complete backup of the entire SMPE environment > *before* the application of any of these PTF's. > > Incidentally, we do have UA95897 applied for over a year now, and have not > run into the scenario that OA58037 describes. Seems like a pretty small > window of problem, and even then, it was on a task/job that was being > cancelled to begin with. I'd probably open ticket with IBM on that APAR, and > ask an opinion (which they may not give). > > __________________________________________________________ > ___________________________________________ > Dave Jousma > AVP | Manager, Systems Engineering > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, > MI > 49546 > 616.653.8429 | fax: 616.653.2717 > > > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Gibney, Dave > Sent: Tuesday, September 17, 2019 2:44 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Considering Bypassing ERROR HOLD for OA58037 > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > Well, I do run VPS/TCPIP > Key Product Name > --- ------------ > 012 DRS > 001 VPS > 004 VPS/PCL > 002 VPS/TCPIP > > z/OS 2.1 at RSU1903 (RSU1908 included in the set that could come on with > the error bypass. > We don't have many printers, but they are all TCP/IP network attached. So > far I've not experienced (or at least not noticed) any of the errors in the > link. > > Since I found the Health Check disappointing, I could consider backing the > bypassed PTFs out. I haven't looked. Are the SMF fields with the USERCSA > data also part of one or more of the PTFs in this chain? There were 27 that > went on with the bypass and selecting UA94607. (And 31 others that had > dependencies satisfied :) ) > > Only running them in the sandboxes for now. > > > -----Original Message----- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > > Behalf Of Brian Westerman > > Sent: Monday, September 16, 2019 9:22 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Considering Bypassing ERROR HOLD for OA58037 > > > > That's part of a pretty long comedy of errors that apply to (mostly) > > LRS's VPSIP product. If you are running VPSIP, like several of our > > sites, then you are likely aware of the issues that this whole string of > > aparas > has caused. > > > > https://urldefense.proofpoint.com/v2/url?u=https- > > 3A__www.ibm.com_support_pages_debchk-2Ddeb-2Dlock-2Dnew- > > 2Dfunction-2Dlist- > > > 2Dmaintenance&d=DwIFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQ > > b- > > > Je7sw&r=u9g8rUevBoyCPAdo5sWE9w&m=RfHnql3CpaS3KFsgCx5LqRORoZTp > > 07SIADw0RnXZmcA&s=4Cib0hikGVj- > > d0uZAk1aIUAIlm51FKWEuYtMho4Ehww&e= > > > > If you are not using VPSIP then it probably won't effect you either > > way to bypass the hold. > > > > Brian > > > > ---------------------------------------------------------------------- > > 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 **CAUTION > EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > This e-mail transmission contains information that is confidential and may be > privileged. It is intended only for the addressee(s) named above. If you > receive this e-mail in error, please do not read, copy or disseminate it in > any > manner. If you are not the intended recipient, any disclosure, copying, > distribution or use of the contents of this information is prohibited. Please > reply to the message immediately by informing the sender that the message > was misdirected. After replying, please erase it from your computer system. > Your assistance in correcting this error is appreciated. > > > ---------------------------------------------------------------------- > 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
