Look for the same, or within a few bytes of, the instruction address where the S0C1 occurred in one or more of the GP registers. It is most likely to be in R15. Look for a probable return address in R14, where probable means that that address can be found in the dump. Look at that address for a BALR R14,R15. If this doesn't work, try looking in the dump for linkage stack entries. You may have taken the wild branch by any one of a dozen different instructions. Long ago there was BALR, B, LPSW, BXH, BXLE, ... Now there is also PC and many other newer ways. PC is associated with a linkage stack. Find the current one, then back up to its predecessor.
Don't rightly know how a translation exception address can be associated with a S0C1. Bill Fairchild Software Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.4503 * Mobile: +1.508.341.1715 Email: [email protected] Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mike Sent: Friday, May 28, 2010 12:27 PM To: [email protected] Subject: No SDWA - TEA I'm shooting a wild branch S0C1 dump - result of a SLIP SET,C=0C1 no SDWA - so no SDWABEA this is z/os 1.10 I note in the trace there is a TEA - in a S0C4 it is the offending page address, but what is the significance of this for a S0C1? Thanks Mike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
