S0C4's don't just happen: they happen on a particular machine instruction and with particular register contents. You look at the instruction, the register contents and the addressing mode and deduce the cause.
A SLIP trap will be no more help than a SYSUDUMP if you are unwilling or unable to do the above. Is the assembly listing unavailable? Did I miss that part? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: Tuesday, February 07, 2017 2:00 PM To: [email protected] Subject: Re: Program now working, but why? Rather than trying to infer the cause by tweaking everything in sight, how about this: Set a SLIP PER trap to catch an SVC dump for the first abend of any kind, S0C4 or otherwise. That dump may tell you the exact cause far more quickly than trial-and-error with recompiles/reassemblies/logic-changes. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
