On Thu, 6 Mar 2014 17:11:17 -0500 David Cole <[email protected]> wrote:
:>I have a question. Recently, I was using z/XDC to watch the flow of
:>execution of some task in a different aspace. At one point, that code
:>acquired the Local Lock and then fell into a closed, tight execution
:>loop ("B *" actually - I guess that's as tight as it gets.)
:>But watching this thing from another aspace, I could not tell where
:>the execution loop was!
:>Normally, I would look at the resume PSW from the newest RB/XSB on
:>the running TCB, but in this case the LLOCK was held, so the RB
:>information was ancient history.
:>So my question is, when the LOCAL LOCK is held and a the aspace that
:>holds it is spinning, and I'm looking in from the outside, where do I
:>look to to find that aspace's current PSW and registers?
:>(Eventually, we took a dump and looked in the System Trace and found
:>the loop from recorded interrupt addresses, but I'd like to be able
:>to figure this out live... without having to resort to a dump.)
You would need to force a store status, which would require a non-masked
interrupt. Try checking the EXT register save area to see if it seems
applicable.
Or do a SIGP STOP/STORE STATUS
Have not done it myself.
--
Binyamin Dissen <[email protected]>
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.
I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
