Re: _FEEDBACK tok_isi interpretation
I thank Tony and Lizette. Janet -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: _FEEDBACK tok_isi interpretation
Janet Graff wrote: >Thanks! I will look into that. To what? Or to who do you say thank you? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: _FEEDBACK tok_isi interpretation
Thanks! I will look into that. Janet -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: _FEEDBACK tok_isi interpretation
My apologies. I'm not trying to solve the U121. I generated that on purpose. I'm working on writing a robust abend handler. It's reporting S0C4 abends nicely but this User abend is coming out as a CEE3250C. Janet -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: _FEEDBACK tok_isi interpretation
On 24 February 2015 at 14:11, Janet Graff <004dc9e91b6d-dmarc-requ...@listserv.ua.edu> wrote: > I have an abend handler that is catching a U121 abend. The LE Abend Handler > is telling me that the facility_id is "CEE" and the tok_msgno is "3250" > giving me > > CEE3250C The system or user abend abend-code was issued. > > abend-code in the message description is in italics in the LE Run-time > Messages manual which makes me think I can get hold of the actual U121 abend > code. Looking at the _FEEDBACK structure I see a field tok_isi which is > documented as " the instance specific information (ISI)" but I can't find any > doc that tells me how this 64 byte field is formatted. > > Does anyone know what the tok_isi contains and how to translate it to get the > instance specific information? I don't, and doubtless an LE expert who does will chime in. But I do think it's unlikely that the ISI is a 64 *byte* field. LE books and the C definitions in SCEEH.H include two different definitions - one 32-bit, and one 64-bit. In C terms, one is int; the other long. In assembler terms, there is only a "DS F" that I can find. Presumably this is the result of my finding a mix of 32-bit and 64-bit environment references. Which is yours? Regardless, by its name this is a token, so in some sense a pointer, but presumably an opaque thing that you aren't supposed to disect on your own. Certainly it doesn't sound likely to actually contain the abend code. It is also called an "index into ISI block" in some places. Ah - I think Lizette was very close. Look at routine CEEGQDT in that same book (LE Programming Reference). "CEEGQDT retrieves the q_data_token from the Instance-Specific Information (ISI). CEEGQDT is particularly useful when you have user-written condition handlers registered by CEEHDLR." And the detail on q_data_token is in the LE Programming Guide under "q_data Structure for Abends ". It contains the abend code and reason code. There's even a COBOL example. Good luck. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: _FEEDBACK tok_isi interpretation
Also, Did you see this entry? And does it help? http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ceea300/clcncod.htm Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Lizette Koehler > Sent: Tuesday, February 24, 2015 6:23 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: _FEEDBACK tok_isi interpretation > > It may be difficult to determine without more detail on the abend and the > environment. > > CICS/IMS/DB2/MQ, etc??? > Is this a program product or home grown function? > > COBOL, PL/I, Assembler code? > > > What other messages appear at the time of the failure? > IXC, IGD, IEE, > > Any region size issues? > > Can you provide the CEEDUMP output? > > Have you opened a case with IBM on this issue? > > Have you used IPCS with VERBX for LEDATA? > > > > Lizette > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM- > m...@listserv.ua.edu] > > On Behalf Of Janet Graff > > Sent: Tuesday, February 24, 2015 12:11 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: _FEEDBACK tok_isi interpretation > > > > I have an abend handler that is catching a U121 abend. The LE Abend > > Handler is telling me that the facility_id is "CEE" and the tok_msgno > > is "3250" giving me > > > > CEE3250C The system or user abend abend-code was issued. > > > > abend-code in the message description is in italics in the LE Run-time > > Messages manual which makes me think I can get hold of the actual U121 > > abend code. Looking at the _FEEDBACK structure I see a field tok_isi > > which is documented as " the instance specific information (ISI)" but > > I can't find any doc that tells me how this 64 byte field is formatted. > > > > Does anyone know what the tok_isi contains and how to translate it to > > get the instance specific information? > > > > Janet > > > > -- > 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
Re: _FEEDBACK tok_isi interpretation
It may be difficult to determine without more detail on the abend and the environment. CICS/IMS/DB2/MQ, etc??? Is this a program product or home grown function? COBOL, PL/I, Assembler code? What other messages appear at the time of the failure? IXC, IGD, IEE, Any region size issues? Can you provide the CEEDUMP output? Have you opened a case with IBM on this issue? Have you used IPCS with VERBX for LEDATA? Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Janet Graff > Sent: Tuesday, February 24, 2015 12:11 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: _FEEDBACK tok_isi interpretation > > I have an abend handler that is catching a U121 abend. The LE Abend Handler > is telling me that the facility_id is "CEE" and the tok_msgno is "3250" giving > me > > CEE3250C The system or user abend abend-code was issued. > > abend-code in the message description is in italics in the LE Run-time > Messages manual which makes me think I can get hold of the actual U121 > abend code. Looking at the _FEEDBACK structure I see a field tok_isi which is > documented as " the instance specific information (ISI)" but I can't find any > doc that tells me how this 64 byte field is formatted. > > Does anyone know what the tok_isi contains and how to translate it to get > the instance specific information? > > Janet > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
_FEEDBACK tok_isi interpretation
I have an abend handler that is catching a U121 abend. The LE Abend Handler is telling me that the facility_id is "CEE" and the tok_msgno is "3250" giving me CEE3250C The system or user abend abend-code was issued. abend-code in the message description is in italics in the LE Run-time Messages manual which makes me think I can get hold of the actual U121 abend code. Looking at the _FEEDBACK structure I see a field tok_isi which is documented as " the instance specific information (ISI)" but I can't find any doc that tells me how this 64 byte field is formatted. Does anyone know what the tok_isi contains and how to translate it to get the instance specific information? Janet -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
