How are you shutting down Websphere/MQ? With BPX you can terminate the threads (PID) if you identify them.
The D OMVS command has a few ways to do this D OMVS,A=ALL then look for your parent task Then D OMVS,P=xxx parent task number Then terminate the threads. I am not familiar with Websphere/MQ and maybe the MQ list could be helpful. To join, if you have not done so, use this URL MQ https://listserv.meduniwien.ac.at/archives/mqser-l.html Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Nai, Dean > Sent: Wednesday, July 05, 2017 7:34 AM > To: [email protected] > Subject: Abend CODE=4C5 REASON CODE=74F62104 > > > 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? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
