Peter thank you Just thinking out loud if I wanted to get infoformation about the load module / pc rtn
As the Estae recovery is now running in the home address space and when it is running home=primary=secondary I am thinking the doc says I can issue CSVQUERY in AR mode I might try to put SDWAPRIM on my DU-AL And and maybe get the name of the PC routine > On Jan 1, 2024, at 10:56 AM, Peter Relson <[email protected]> wrote: > > Joe R wrote > <snip> > Seems that sdwaec2 points to the code in the pc routine while sdwaec1 points > the home address space right after the pc instruction wondering if I can > always make this assumption > </snip> > > As Walt F pointed out, there is documentation about these fields in the > assembler services guide. I think that makes it clear what is in SDWAEC1 and > SDWAEC2 under which circumstances. > > As to the assumption about "the home address space", that would be a valid > assumption only if you know that the primary address space equaled the home > address space at the time of the instruction (PC in this case), which is not > in general the case. The PC would have been an instruction in the pre-PC > primary address space. > > Do note that instructions are fetched from the home address space (not the > primary address space if the two differ) for home ASC mode. > But since you cannot issue a PC in home ASC mode, that does not apply to your > case. And in practice, all code that uses Home ASC mode is in common storage. > > <snip> > My question is there any field in the SDWA or extensions that would tell me > in what ASID the abend occurred > </snip> > I'd look at SDWAXM, specifically SDWAPRIM, unless the error was in home ASC > mode in which case you don't need to look at the SDWA but can use PSAAOLD -> > ASCBASID. SDWAPRIM is the primary ASID at the time of error. Is that what you > mean by "in what ASID the abend occurred"? If the error was a storage access > using an ALET, the erroneous reference could have been to any number of > (address or data) spaces. > > You seem to be pursuing something that might not be overly useful for a > recovery routine. The recovery routine of the PC issuer would typically rely > on footprints set by the PC issuer's mainline to understand what the mainline > was last doing (and thus how the recovery routine needed to react). The > recovery routine of the PC target would typically not care about where the PC > was issued from. A diagnostician, of course, might well care about both, but > they would typically be looking at a dump. > > Peter Relson > z/OS Core Technology Design > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
