Peter, Thanks for extra information. However, your somewhat cryptic message doesn't really clarify which field I should use.
I think the question I need to ask is, Under what circumstances is the ASSBISQN field different from the ASTE1IN field? The code in question is for a diagnostic utility I wrote about 20 years back. It only ever examines fields in the secondary address space. It has an error recovery routine which has proved robust over the years. It has been reporting the 0D3-0013 abends for a while and recovering gracefully. Lennie Dymoke-Bradshaw -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Peter Relson Sent: 19 November 2020 14:01 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Finding the STEIN of another address space ASSBISQN is not always the same as the ASTE Instance Number (ASTE rather than STE). Maybe the back-handed hint is that this is not something you should be doing? I wouldn't go that far. Architecturally, the ASTE instance number is in the ASTE. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
