The point of the post was that this was something weird which someone might
have experienced.
Anyway, here is what we see:
Input:
//SORT EXEC PGM=SORT
//SYSIN DD *
SORT FIELDS=(61,100,CH,A,265,2000,CH,A)
SUM FIELDS=NONE
END
//*
Organization: PS
Record format: FB
Record length: 2285
Block size: 27420
Output:
09.04.03 JOB50717 +WER999A XSSYC801,SORT , - UNSUCCESSFUL SORT
0C4 S
9.04.04 JOB50717 IEA995I SYMPTOM DUMP OUTPUT 036
036 SYSTEM COMPLETION CODE=0C4 REASON CODE=00000010
036 TIME=09.04.03 SEQ=47706 CPU=0000 ASID=004D
036 PSW AT TIME OF ERROR 078C0000 80E795C4 ILC 4 INTC
10
036 NO ACTIVE MODULE FOUND
036 NAME=UNKNOWN
036 DATA AT PSW 00E795BE - B20AF000 1BFF9180 202AA714
036 AR/GR 0: 00AFE040/00000000 1: 00000000/2000CFBC
036 2: 00000000/2000CFBC 3: 00000000/00E7A018
036 4: 00000000/00ACF708 5: 00000000/00AFD830
036 6: 00000000/00E794C0 7: 00000000/00FAA380
036 8: 00000000/00000000 9: 00000000/01755508
036 A: 00000000/00AFD8F0 B: 00000000/2000CFBC
036 C: 00000000/010DAEE0 D: 00000000/00026120
036 E: 00000000/00FF0F00 F: 01000002/00000000
036 END OF SYMPTOM DUMP
Changing the SORT to use these parms instead:
SORT FIELDS=(61,100,CH,A,265,1940,CH,A)
makes the problem go away.
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: "Gibney, Dave" <[email protected]>
To: [email protected],
Date: 04/12/2012 09:49
Subject: Re: SYNCSORT
Sent by: IBM Mainframe Discussion List <[email protected]>
AS is often the case, without the sort statements, file attributes and
actual error messages, I doubt any of us are psychic enough to give a
meaningful answer.
Dave Gibney
Information Technology Services
Washington State University
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Anthony Fletcher
> Sent: Monday, December 03, 2012 12:47 PM
> To: [email protected]
> Subject: SYNCSORT
>
> 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
