A quick search of the archives reveals that this question has been asked
several times over the years. Here is a reply from Shmuel in 2006:
>BPXP018I THREAD 0DDE140000000000, IN PROCESS 16777595, ENDED WITHOUT
>BEING UNDUBBED WITH COMPLETION CODE 0033E000,
>AND REASON CODE 00000000.
Sounds like CICS is doing a DETACH for a task that hasn't had time to shut down
cleanly.
Shmuel (Seymour J.) Metz, SysProg and JOAT
Reference:
https://listserv.ua.edu/cgi-bin/wa?A2=ind0608&L=IBM-MAIN&P=R45915&I
Regards,
Greg Shirey
Ben E. Keith Company
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John Mattson
Sent: Thursday, January 19, 2017 3: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
