This abend was caused by doing ISGENQ OBTAIN twice per Ed Jaffe suggestion
I’m now thinking if cannt get the info from the RB/CDE I can try CSVQUERY But truth is you right that still might not get me an answer Because this particular module was in the NUCULES I can do a NUCLKUP That may give name if I do BYADDR and supply the PSW But I dint think it would give me the length Thanks > On Feb 24, 2024, at 6:12 PM, Peter Relson <[email protected]> wrote: > > The value is the time of error PSW from wherever it came. It could have come > from a task or SRB in this address space. It could have come from an SRB in > another address space. It need not be in "RBOPSW" (or XSBOPSW16) of any RB. > > Most of your recent questions ought to be preceded by a description of what > it is that you are trying to do. It is not helpful, either to you or to those > whom you are asking, to keep asking questions that you (and a program) should > not have to care about. I'm guessing that this is another thing you are > trying to do to help name the program that blew up. Fine. But how does being > in RBOPSW of some task's RB help other than to give a name to the most recent > PRB that had a CDE? Even if that's the jobstep program's PRB, is that what > you want to surface? > > The odds are that there is no intended programming interface that will do > what you want (whatever that is) in all cases. And no one is going to try to > figure out the exceptions. > > 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
