After further research it looks like what is happening is the problem BPXAS address space eventually ends but later in the day, when another one starts, it uses the same address space ASID=01B4 and the cycle starts all over again. Anyone have any ideas on how to tell Z/OS or OMVS to mark this address space as unusable?
On 7/5/17, 11:02 AM, "IBM Mainframe Discussion List on behalf of Nai, Dean" <[email protected] on behalf of [email protected]> wrote: >That identifies it as TCPIP which we got from the error messages and dumps. >But seeing it's cleaner to IPL than to recycle TCPIP on our Production LPAR I >was hoping someone else had this same problem and had a work around better >than the one we have. But thanks for your input. Really appreciated. > > > > > > > >On 7/5/17, 10:52 AM, "IBM Mainframe Discussion List on behalf of Allan >Staller" <[email protected] on behalf of [email protected]> wrote: > >>1st try TSO BPXMTEXT 74F62104 >>It may give you some clues. >> >> >><snip> >>Has anyone else run into these abends for OMVS jobs? There is an APAR out >>there that recognizes the issue but has no solution. >>What seems to be happening is we have a Websphere running in one of the BPAXS >>and it gets recycled everyday by canceling it because it won't come down >>clean because of active threads. This has been causing the BPXAS that the >>Websphere was running in to cause everything else in it to get these abends. >>As a temporary solution we have been draining the problem BPXAS by issuing >>this command f bpxoinit,shutdown=forkinit so no new work goes into it but >>lately some of the new BPXAS that have started have the same problem. Anyone >>have any idea's? >></snip> >> >> >> >>::DISCLAIMER:: >>---------------------------------------------------------------------------------------------------------------------------------------------------- >> >>The contents of this e-mail and any attachment(s) are confidential and >>intended for the named recipient(s) only. >>E-mail transmission is not guaranteed to be secure or error-free as >>information could be intercepted, corrupted, >>lost, destroyed, arrive late or incomplete, or may contain viruses in >>transmission. The e mail and its contents >>(with or without referred errors) shall therefore not attach any liability on >>the originator or HCL or its affiliates. >>Views or opinions, if any, presented in this email are solely those of the >>author and may not necessarily reflect the >>views or opinions of HCL or its affiliates. Any form of reproduction, >>dissemination, copying, disclosure, modification, >>distribution and / or publication of this message without the prior written >>consent of authorized representative of >>HCL is strictly prohibited. If you have received this email in error please >>delete it and notify the sender immediately. >>Before opening any email and/or attachments, please check them for viruses >>and other defects. >> >>---------------------------------------------------------------------------------------------------------------------------------------------------- >> >> >>---------------------------------------------------------------------- >>For IBM-MAIN subscribe / signoff / archive access instructions, >>send email to [email protected] with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
