Arney is right, Lou. I don't know what "your debugger" is, but any
debugger will allow you to step through your instructions one at a
time so that you can see exactly(!) what is and is not happening.
John Gilmore also is right. You are simply not providing complete
information. What you have provided leaves many pertinent questions
unanswered. Examples:
- What is in R14?
- What is STATIC_EYE's length attribute?
- What is the content of storage at STATIC_EYE?
You need to provide more than just the code snippet. You need also to
provide assembly listing snippets showing both your code and all code
and data that sets up the inputs to your code snippet.
Notice above that I said "Assembly listing snippets". I did not say
source code snippets.
At this point you are giving answers to all questions but since your
results conflict what your answers imply your results should be,
clearly your answers are wrong. So we need to see the code.
Or you need to use an interactive debugger. My favorite, of course,
is XDC, but even TSO TEST would be adequate for solving this issue.
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: <mailto:[email protected]>[email protected]
Home page: www.colesoft.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube/colesoftware
At 8/19/2014 06:48 PM, Chuck Arney wrote:
Lou, why are you not using your debugger to trace these 5 instructions?
That would show you exactly what is going on. There is no need to guess.
At the very least blow it up with a program check rather than use a system
service that will modify registers in the process.
Chuck Arney
Arney Computer Systems
Web: http://zosdebug.com
Facebook: http://www.facebook.com/arneycomputer
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: <mailto:[email protected]>[email protected]
Home page: www.colesoft.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
