> Does anyone on this list still write code? If you want to call it that :-)
Seriously, I have wanted this feature since I started writing assembler code in 1969. Debugging h*ll: if it's not R14, look for ANY register that points to a suspect BAL or BALR. Then hope you can find a non-suspect BAL(R) and work your way forward. And as others have pointed out, the newish Jumps only made it worse. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Edward E. Jaffe Sent: Friday, July 29, 2005 1:56 PM To: [email protected] Subject: Wild Branch Diagnosis (Was: Five Digit Device Numbers) OK. So nobody cares about 5-digit device numbers (JOBCAT/STEPCAT is always an amusing topic). How about the wild branch diagnosis improvement? (Does anyone on this list still write code?) z9 109 remembers the last successful branch instruction address and the operating system displays that address in dumps. I would guess that at least 90% of S0C1 abends are caused by so-called "wild branches" ... a large percentage of which end up at location zero. Given that, a typical debugging scenario is to look for zeros in R15. If so, assume the return address in R14 is the last known address. But what if it isn't? What if all of the registers are "clobbered"? There are many different possible wild branch outcomes and some can be *extremely* difficult to diagnose (BTDTGTS). My reaction? It's about time! Thank you, IBM! ---------------------------------------------------------------------- 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
