Not familiar with your specific situation but very familiar with the message. If you have an application that interfaces to USS and ends without terminating the connections neatly you see this message. Seems to be utterly harmless and has no real effect.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Mattson Sent: Thursday, January 19, 2017 1:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: BPXP018I THREAD ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0033E000 , AND REASON CODE 00000000 Going to CICS TS 5.2 and noticed this message when the CICS region comes down. zOS 1.13 DB2 and IMS It looks like OMVS is FULL ACTIVE. So why getting this message when CICS Region comes down? +DFHTM1703 TCICS01 CICS is being terminated by userid CICSMTO in transaction CESD. BPXP018I THREAD 0D8D8B0000000000, IN PROCESS 124, ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0033E000 , AND REASON CODE 00000000. "D OMVS" gives BPXO042I 12.59.18 DISPLAY OMVS 904 OMVS 000E ACTIVE OMVS=(00) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
