I think I'm safe. Not nearly this volume and no dependency in SYS1.IMAGELIB
> -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Brian Westerman > Sent: Wednesday, September 18, 2019 1:12 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Considering Bypassing ERROR HOLD for OA58037 > > When you are only about 1/2 thorough the apar list, if you print more than > 1000 jobs before restarting VPSIP, it would abend, the jobs all needed to > use|need SYS1.IMAGELIB. Then when we got to #18 on the list, the site > could produce 84,000+ jobs (again all needed SYS1.IMAGELIB), before the > abend. Now with the next 3 apars, we appear to be able to print an > unlimited number of jobs, but we split VPSIP into two separate regions and > restart them both weekly just in case, but once we get the final 2 on, we will > probably try to go without restarting any more. > > BRian > > > On Tue, 17 Sep 2019 18:44:02 +0000, Gibney, Dave <gib...@wsu.edu> > wrote: > > >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 > > ---------------------------------------------------------------------- > 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