Thanks to all for the helpful comments. Turned out to be that a z/OS 1.13 compatibility fix was required and had been missed - SY69690. Various symptoms from that only one of which was the S0C4-10. SY69691 is the same problem for version 1.4, so needs to be on for z/OS 1.13 and later.
regards, Anthony Fletcher - NZ MIITP Team Lead NZ SMM (AirNZ, Westpac NZ , TelstraClear NZ and NWM AU) IBM Strategic Outsourcing Delivery Server Systems Operations Server Management Mainframe Mainframe Software Program Manager NZ z/OS Technical Lead A/NZ Ph: Direct +64 4 576 8142, tieline 61 929 8142, ITN *869298142, mobile +64 21 464 864, Fax +64 4 576 5808. Internet: [email protected], Sametime: [email protected] "The biggest threat to effective communication is the belief that it has occurred" "Winners make commitments, Losers make promises" From: Anthony Fletcher/New Zealand/IBM@IBMNZ To: [email protected], Date: 04/12/2012 09:47 Subject: SYNCSORT Sent by: IBM Mainframe Discussion List <[email protected]> Any SYNCSORT users out there? We have one job that gets an S0C4-10. The problem can be reproduced with a three line set of data, so its not a capacity problem. There are two sort fields. If the second one's displacement is reduced the problem goes away but it otherwise looks like an addressing problem. The sort length plus displacement is nowhere near as long as the LRECL of the data set. The abend does not appear to be in any SYNCSORT module. It is version 1.3.0 running on z/OS 1.13. Waiting for vendor agent to get back. Anyone experienced anything like this? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
