I wouldn't think that more than one of the 0C4's in the system trace would match the PSW in the MCH control block. You can display time in the system trace by doing 'ip systrace time(local)'. For the wrapping issue... some version of z/OS allowed the system trace table size to be set much higher. I recently asked our guys to bump up to 12M and that seems to be working for now.
In article <2013103444541247.wa.ronmacraehotmail.co...@listserv.ua.edu> you wrote: > Lizette, > I can get the registers and PSW no problem. The problem I have is > getting the TIME of the S0C4 so I can see which one is first. So much > happens before LE gets round to taking a system dump that the z/OS trace has > wrapped and I can't tell which of the 6 S0C4 abends, on different TCBs, was > first. I don't think I can assume that the first to produce a CEE dump or the > first to produce a SYSMDUMP was the first as they seem to preempt each other. > Anyway I got round the problem by slipping on the instruction that sets us up > to fail by setting a control block pointer to zero before any of the TCBs > S0C4ed. > However it would have been nice to be able to tell the time of the S0C4s. > Ron. -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive sas...@sas.com (919) 531-5637 Cary, NC 27513 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
