To be clear, the TEA is only relevant for Translation Exceptions, and a PIC 4 is not. Notwithstanding that your trace entry example *is* a PIC 4, and that is great information.
Frankly, I think it was unwise by z/OS to lump translation exceptions (PICs 10, 11, 39-3B) in with S0C4. There's a fundamental difference between attempting to access storage with the wrong key, and storage that doesn't exist (S0C5 is a variant). S0D0 for the latter would have make sense. I'm quite clear that changing such things isn't practicable. sas On Fri, Apr 28, 2023 at 12:52 PM Ed Jaffe <edja...@phoenixsoftware.com> wrote: > On 4/28/2023 1:32 AM, Robin Atwood wrote: > > @Ed Jaffe: thanks for the tip about the TEA, but where do you find it? > IPCS STATUS FAILDATA displays it but, in my dumps, PSA+90 and PDS+A8 both > have zero in the address part. > > The TEA is displayed on various IPCS displays. It's captured for the > SDWA at just the right time. I think the PSA fields could be overlaid > before they are dumped, so I would never trust them. > > Personally, my favorite "go to" after inspecting PSW and registers is > the SYSTRACE. (I did a GSE UK pitch on that in November and a reprised > it as a SHARE pitch in Atlanta.) For example, a protection exception: > > 0004 0149 03923F00 PGM 004 00000000_1747106C 00060004 00000000 > 47140000 80000000 7F328404 <-- Here! > 0004 0149 03923F00 *RCVY PROG 940C4000 00000004 > > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
