>Thanks for clarifying. Could you select / re-select the Address space (other >TCB?) to be used in >your dump analysis?
Yes, I set a symbol to the desired TCB address and then the analysis proceeds correctly. > Could you get any info from Logrec? It's a client's system, so I look at what I am given. Anyway, I found the bad branch from the BEAR, a routine address in an internal control block had been stomped on. By what and when remains a mystery. -Robin -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: 23 May 2013 14:29 To: [email protected] Subject: Re: Mysterious Abend 0C1 Robin Atwood wrote: >OK, this is what happened. The "dump analyser" is a trusty clist written for >IPCS by me over 20 years ago. It (almost always) works by using the chain: >ASXB -> abending TCB -> RTWA, from where it gets the PSW and registers. In >this case it got caught out because there was a preceding TCB with a >completion code of 0C1 but only a PRB, no RTWA and hence the mayhem. Thanks for clarifying. Could you select / re-select the Address space (other TCB?) to be used in your dump analysis? >So, sorry for the noise but this exchange has proved very useful because I now >know about the BEAR. Unfortunately it is not listed by either the IPCS STATUS >or SUMMARY commands, which would have been very useful since there is a chain >of control blocks to follow (SDWAXPAD->SDWAPTRS, SDWAXEME->SDWARC4). SDWARC4. Hmmm, I now rememeber. EREP does show the Breaking-Event-Address Register. Could you get any info from Logrec? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
