All I want to do at this point is determine where the mismatching BAKR/PR occurs. We can't "see" which is the active stack entry, but can at least compare the the contents of the stacked registers in the current entry before/after a suspect call and assume there's a mismatch if they're different. The empty stack condition is a non-issue as it turned out the invoking program using BAKR/PR so if we encounter an empty stack condition it is also a mismatch.
Robert Ngan CSC Financial Services Group From: Binyamin Dissen <[email protected]> To: [email protected] Date: 2011/12/10 15:23 Subject: Re: Quick test for empty stack? Sent by: IBM Mainframe Assembler List <[email protected]> On Fri, 9 Dec 2011 12:29:05 -0600 Robert Ngan <[email protected]> wrote: :>Is the a quick/simple test to determine whether the linkage stack is empty? :>Someone is getting a S0E0 abend with interrupt code of X'34'. I suggested :>bracketing calls to any "suspect" programs with a dump of the results from :>ESTA, however the POPS indicates you may get an exception if the stack is :>empty. Is there a quick and dirty check we can do to test for an empty :>stack instead of having to set up a error handler to handle the empty stack :>exception? How will you use this information? Will the logic (which EXPECTS that there is a stack entry) discovers that there ain't none, what will it do? -- 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.
