How grown application written in ASM and C. Works fine since years, except for some "out of socket descriptor" problems every now and them. I was asked to help finding the cause of S23E or S53E (both DETCH) abends since the developer tries to fix the above "ourt of socket descriptor" problem.
I have set SLIP traps to catch the S23E or S53E. I do have some svcdumps. I have found some hints in the dump. I suspect some storage overlay but am stuck at the moment. Need some fresh ideas. >From the system trace I see that the S23E or S53E is preceeded by an S202 and >sometime a true PGM 011. Some questions: a) I see a couple of FREEMAIN (SSRV 78) trace entries pointing to a TCB in read/write nucleus (TCB address is 00FDD4F8). Do these hold some useful information for me? b) I know "SVC D" is also entered for normal task termination. In an oooold MVS debugging manual I found that the first byte of R1 is x'08' this indicates RTM2 is called for task termination cleanup. The x'08 does no longer seem to hold true. How can I identify such an non-error an SVC D entry? c) In some dumps I see "SVC 3" (exit) trace entries, sometimes I can see the "SVC 3E" (DETACH), sometime it is not in the trace. Thoughts? -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
