Agrrr.. Sorry for the misformatted mail. Trying again.
I'm chasing another problem where an LE program (COBOL) gets into an endless, rather tight loop in CEEPLPKA after an S04E abend I'm trying to understand the relation between I/O interrupt system trace entries, and a pair of SSRV entries that very often follow the I/O entry. Here is a sample sequence from the trace: 0003 031C 009FEA30 DSP 00000000_0872C4B6 00000000 00000000 26C62364 0003 031C 009FEA30 EXT TIMR 00000000_0872BFAE 00001005 0001 031C 009FEA30 DSP 00000000_0872BFAE 00000000 00000000 26C62364 0001 031C 009FEA30 I/O 06B16 00000000_0872C2C8 00104007 745786C0 0001 031C 009FEA30 SSRV 11F 9EE5C3D6 16701A80 80000000 157A25F8 0001 031C 009FEA30 SSRV 150 02F5F020 00000000 7EB06940 00000000 The program is dispatched (DSP), interrupted at end of time slice (EXT TIMR), dispatched again (DSP), then interrupted by an I/O which completed (I/O). Very often, two system service calls (SSRV), first for RELEASE (SSRV 115), second for DFSMS Media Manager ICYDIE (SSRV 150) are seen. First I thought the SSRVs are related to the program, but I now have my doubts. I'd rather think they are caused by I/O interrupt handling. Especially, since I have seen such sequences in another dumps, although much less often. Can anyone say something about the nature of those SSRV calls. Am I safe to say they do not belong to the problem at hand? — Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
