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!
--
.-----------------------------------------------------------------.
| Edward E. Jaffe | |
| Mgr, Research & Development | [EMAIL PROTECTED] |
| Phoenix Software International | Tel: (310) 338-0400 x318 |
| 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801 |
| Los Angeles, CA 90045 | http://www.phoenixsoftware.com |
'-----------------------------------------------------------------'
----------------------------------------------------------------------
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
