@Jim and @Chris, I think you have it. Thanks! Yes, the task has an STIMERM exit that POSTs one of the ECBs and there is some evidence to indicate that the ABEND is at least approximately when the timer should have popped.
SRBs and termination do not seem to be likely participants. The interesting thing is that the application was running perfectly for some time and only started doing this after the customer applied RSU1606. It has since started doing it "a lot." On to a real dump! No, the LE dump does not include a trace table. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jim Mulder Sent: Wednesday, September 28, 2016 11:01 PM To: [email protected] Subject: Re: Interpreting an S202-0000 That's a good guess. I think by the time LE's ESTAE gets control, the timer exit IRB would be gone. LE might be going back two RBs (skipping over the RTM2 SVRB) to fetch the PSW it is displaying, Other possibilities would be that an ancestor TCB got the 202 abend and is terminating, and RTM2 is detaching a waiting subtask, under which LE's ESTAE took this dump. Or an SRB did the POST that got the 202 abend, and SRB-to-task percolation is ABTERMing this waiting task. Jim Mulder z/OS Diagnosis, Design, Development, Test, etc. IBM Corp. Poughkeepsie, NY IBM Mainframe Discussion List <[email protected]> wrote on 09/29/2016 01:04:08 AM: > From: "Webster, Chris" <[email protected]> > To: [email protected] > Date: 09/29/2016 01:55 AM > Subject: Re: Interpreting an S202-0000 Sent by: IBM Mainframe > Discussion List <[email protected]> > > Abend S202 and SVC 1 are out of synch. Do you have a timer exit doing > a post? It would run under the same TCB but a different RB and if LE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
