BPXP018I THREAD ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0033E000 , AND REASON CODE 00000000

John Mattson

unread,

Jan 19, 2017, 4:18:54 PM1/19/17

to

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 list...@listserv.ua.edu with the message: INFO IBM-MAIN

Greg Shirey

unread,

Jan 19, 2017, 4:25:20 PM1/19/17

to

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

Allan Staller

unread,

Jan 19, 2017, 4:26:03 PM1/19/17

to

See System 33e Abend.

It is either mother task ended without notification to daughter task or vice-versa.

Most likely something is missing in the shutdown sequence.

HTH,

<snip>

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)

</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.

----------------------------------------------------------------------------------------------------------------------------------------------------

Charles Mills

unread,

Jan 19, 2017, 4:28:18 PM1/19/17

to

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-...@LISTSERV.UA.EDU] On Behalf Of John Mattson
Sent: Thursday, January 19, 2017 1:19 PM
To: IBM-...@LISTSERV.UA.EDU