BPXP018I message when STC cancelled
I have an authorized STC that shuts down normally when it is stopped (/P). When I cancel the STC, my ESTAEs are driven from newest to oldest. But I get the message shown below after the ESTAEs are finished. I do TCP/IP calls using IEZASMI in 2 sub-tasks. The 2 sub-tasks that do TCPIP cleanup and issue TERMAPI in their ESTAEs. The thread id is for the JOB STEP TCB. I'd like to undub my address space but don't know what to do. The Unix Callable Services doesn't seem to have a function to do that. I'd set a SLIP trap but this situation doesn't seem slipable. Any help would be appreciated. Thanks in advance, Pierre. 14.33.43 STC00663 BPXP018I THREAD 1B216000, IN PROCESS 33620001, ENDED 039 039 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 40222000 039 , AND REASON CODE . -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BPXP018I message when STC cancelled
Try mvsprocclp: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb100/mpc.htm In article <4960377789730171.wa.prf51videotron...@listserv.ua.edu> you wrote: > I have an authorized STC that shuts down normally when it is stopped (/P). > When I cancel the STC, my ESTAEs are driven from newest to oldest. > But I get the message shown below after the ESTAEs are finished. > I do TCP/IP calls using IEZASMI in 2 sub-tasks. > The 2 sub-tasks that do TCPIP cleanup and issue TERMAPI in their ESTAEs. > The thread id is for the JOB STEP TCB. > I'd like to undub my address space but don't know what to do. > The Unix Callable Services doesn't seem to have a function to do that. > I'd set a SLIP trap but this situation doesn't seem slipable. > Any help would be appreciated. > Thanks in advance, Pierre. > 14.33.43 STC00663 BPXP018I THREAD 1B216000, IN PROCESS 33620001, > ENDED 039 >039 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 40222000 >039 , AND REASON CODE . -- Don Poitras -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BPXP018I message when STC cancelled
I have always seen that message when one of my dubbed applications ends abnormally. I have never figured out exactly what the variables are. I never worried about it, because (a.) it's an "I" message so "nothing to worry about" and (b.) you're already in an ABEND situation: I focus on solving the ABEND, not on worrying about the side effects of the ABEND. That said, what exactly does the message mean and how can you get rid of it? I always kind of figured -- without real evidence -- that the cause of the message was some "unfinished business" on the USS side of things: an open file, a running process, something of that sort. You might try making sure that every UNIX file has been closed and every UNIX process has ended. I suppose one might try to create a test program that triggered the message even without an ABEND: what happens if you open a UNIX file and then end "normally" without closing it? Or starting up a UNIX process and ending "normally" without stopping the UNIX process? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Pierre Fichaud Sent: Saturday, September 19, 2020 12:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: BPXP018I message when STC cancelled I have an authorized STC that shuts down normally when it is stopped (/P). When I cancel the STC, my ESTAEs are driven from newest to oldest. But I get the message shown below after the ESTAEs are finished. I do TCP/IP calls using IEZASMI in 2 sub-tasks. The 2 sub-tasks that do TCPIP cleanup and issue TERMAPI in their ESTAEs. The thread id is for the JOB STEP TCB. I'd like to undub my address space but don't know what to do. The Unix Callable Services doesn't seem to have a function to do that. I'd set a SLIP trap but this situation doesn't seem slipable. Any help would be appreciated. Thanks in advance, Pierre. 14.33.43 STC00663 BPXP018I THREAD 1B216000, IN PROCESS 33620001, ENDED 039 039 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 40222000 039 , AND REASON CODE . -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: BPXP018I message when STC cancelled
Pierre, I'd love to hear if you find a resolution. I have a process with similar behavior and I receive the same message for each sub-task when it terminates within the ESTAE. Thank you, Brian Chapman On Sun, Sep 20, 2020 at 9:49 AM Charles Mills wrote: > I have always seen that message when one of my dubbed applications ends > abnormally. I have never figured out exactly what the variables are. I > never worried about it, because (a.) it's an "I" message so "nothing to > worry about" and (b.) you're already in an ABEND situation: I focus on > solving the ABEND, not on worrying about the side effects of the ABEND. > > That said, what exactly does the message mean and how can you get rid of > it? I always kind of figured -- without real evidence -- that the cause of > the message was some "unfinished business" on the USS side of things: an > open file, a running process, something of that sort. You might try making > sure that every UNIX file has been closed and every UNIX process has ended. > > I suppose one might try to create a test program that triggered the > message even without an ABEND: what happens if you open a UNIX file and > then end "normally" without closing it? Or starting up a UNIX process and > ending "normally" without stopping the UNIX process? > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Pierre Fichaud > Sent: Saturday, September 19, 2020 12:49 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: BPXP018I message when STC cancelled > > I have an authorized STC that shuts down normally when it is stopped (/P). > When I cancel the STC, my ESTAEs are driven from newest to oldest. > But I get the message shown below after the ESTAEs are finished. > I do TCP/IP calls using IEZASMI in 2 sub-tasks. > The 2 sub-tasks that do TCPIP cleanup and issue TERMAPI in their ESTAEs. > The thread id is for the JOB STEP TCB. > > I'd like to undub my address space but don't know what to do. > The Unix Callable Services doesn't seem to have a function to do that. > I'd set a SLIP trap but this situation doesn't seem slipable. > Any help would be appreciated. > Thanks in advance, Pierre. > > 14.33.43 STC00663 BPXP018I THREAD 1B216000, IN PROCESS 33620001, > ENDED 039 >039 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 40222000 >039 , AND REASON CODE . > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
