IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

SyncSORT Abend: S066 RC=4


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
socker_dad

Active User


Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA

PostPosted: Mon Jul 16, 2012 6:42 pm
Reply with quote

I got an odd SyncSORT abend this weekend - SyncSORT abended with a S066 error, reason code 4.

Code:
+WER999A MAC90515,MAC90515,SORT01  -  UNSUCCESSFUL SORT 066 S REASON=00000004


The SYSOUT for the sort step showed the sort parameters, but nothing else.

The JES Message log shows:
Code:

SHL120I ------------------------------------------------------------------------ 
                       S t e p   E n d   S t a t i s t i c s                     
                                                                                 
Step Name: SORT01        Cond Code: S066          Start: 14-Jul-2012 01:52:36 AM 
Step  Num: 4             PGM  Name: SORT          End:   14-Jul-2012 01:52:44 AM 
CPU (TCB): 00:00:01.09   Res Group: DB2ADHOC      Storage below 16M:      3,080k 
CPU (SRB): 00:00:00.02   Srvclass : BATPARAL      Storage above 16M:     22,424k 
Trans Act: 00:00:08.25   Report CL: @ESPD###      Service Units:      69,015,503 
Tape Mnts: 0             SCHENV : MVS#BATCH#TAPE  Total EXCPs:             1,127 
                                                                                 
Unit-- DDName-- EXCP Count-- Blksize        Unit-- DDName-- EXCP Count-- Blksize 
7421 D SORTIN            384  18,200        7121 D SORTWK01           75       0 
7321 D SORTWK02          192       0        7021 D SORTWK03          143       0 
7221 D SORTWK04          128       0        7223 D SYSIN               4   9,040 
7221 D SORTWK05           42       0        7121 D SORTWK06           24       0 
                                                                                 
Total DASD EXCPs:                992        Total Tape EXCPs:                  0 
                                                                                 
SHL121I ------------------------------------------------------------------------ 


The JCL is:
Code:

//SORT01  EXEC PGM=SORT,TIME=1439,PARM='SIZE=MAX,MSG=AP'   
//SYSUDUMP DD SYSOUT=Y                                     
//ABNLDUMP DD DUMMY                                       
//SYSOUT   DD SYSOUT=*                                     
//SORTIN   DD DSN=A.MAG90800.ACTLPREM(&S01),DISP=SHR       
//         DD DSN=A.MAC90615.ACTLCLAM(&S01),DISP=SHR       
//         DD DSN=A.MAC50615.ACTLCLAM(&S01),DISP=SHR       
//SORTOUT  DD DSN=A.MAC90515.SORT.FILE(+1),       
//            DISP=(,CATLG,DELETE),DATACLAS=EXTCOMP
//SORTWK01 DD UNIT=WORK,SPACE=(CYL,(300,200))     
//SORTWK02 DD UNIT=WORK,SPACE=(CYL,(300,200))     
//SORTWK03 DD UNIT=WORK,SPACE=(CYL,(300,200))     
//SORTWK04 DD UNIT=WORK,SPACE=(CYL,(300,200))     
//SORTWK05 DD UNIT=WORK,SPACE=(CYL,(300,200))     
//SYSIN    DD DSN=STATP.SORTLIB(MAC90500),DISP=SHR
//*                                               


The files aren't all that large (OK, the first one is rather popular) - input statistics are:
A.MAG90800.ACTLPREM(0) 53,742 tracks, 2,095,912 records
A.MAC90615.ACTLCLAM(0) 0 tracks, (empty)
A.MAC50615.ACTLCLAM(0) 834 tracks, 32,520 records

All three files are defined as:

Organization . . . : PS
Record format . . . : FB
Record length . . . : 1400
Block size . . . . : 18200
1st extent megabytes: 2798
Secondary megabytes : 200

Unfortunately, the online help for SynsSORT offers no explanation for the error code.

Any ideas?
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Mon Jul 16, 2012 6:58 pm
Reply with quote

Quote:
+WER999A MAC90515,MAC90515,SORT01 - UNSUCCESSFUL SORT 066 S REASON=00000004
Is this the only WERxxxX message in the SYSOUT? No "B" messages? If no "B" messages, suggest you execute the job with following:
Code:
//$ORTPARM DD *
MSG=AP,LIST,BMSG,GMSG

This should produce some additional diagnostic messages.
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Mon Jul 16, 2012 7:00 pm
Reply with quote

And WER999A is very generic SyncSort messages - which just indicates that an error condition occurred, preventing the successful completion of the sort.

It might or might not mean that SyncSort was responsible for the error. So diagnostic info, I asked earlier might help us.
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL

PostPosted: Mon Jul 16, 2012 7:11 pm
Reply with quote

S066 is a dispatcher error. I think you'll need to pull your sysprogs in on this one.
Back to top
View user's profile Send private message
socker_dad

Active User


Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA

PostPosted: Mon Jul 16, 2012 7:16 pm
Reply with quote

Very good - I'll add that to the JCL and attempt to recreate the error.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Mon Jul 16, 2012 9:25 pm
Reply with quote

Hello,

Code:
//SORTIN   DD DSN=A.MAG90800.ACTLPREM(&S01),DISP=SHR       
//         DD DSN=A.MAC90615.ACTLCLAM(&S01),DISP=SHR       
//         DD DSN=A.MAC50615.ACTLCLAM(&S01),DISP=SHR

Possibly a typo on the 2nd and 3rd datasets?
Oops - can't read. . . icon_confused.gif

Code:
//SORTOUT  DD DSN=A.MAC90515.SORT.FILE(+1),       
//            DISP=(,CATLG,DELETE),DATACLAS=EXTCOMP

Has the gdg base been defined?
Back to top
View user's profile Send private message
socker_dad

Active User


Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA

PostPosted: Tue Jul 17, 2012 3:08 am
Reply with quote

Well, the error can't be created today and the system programmers are scratching their heads.

The data storage gurus insist that it wasn't a DASD issue or we would have seen either a B37 or S0C4 (or was it S0C1?).

The SyncSort gurus have no idea.

However, both groups think we should output the sort to a tape file, and increase the exit parameter from 100,000 to 2,500,000 (E100000 to E2500000) since we are sorting around 2 million records.

So we've made the changes and we will see what happens.

This is a historical transaction file which grows about 150,000 - 200,000 records a night, and gets archived at the end of the month - when we start with a fresh, new empty file.

What's weird is that the file is no larger than it has been at this time of the month in the past and no abends occurred then. My personal vote is a resource contention issue that has since resolved since the SyncSort parameters have been static for over three years and SyncSort doesn't abend on a whim.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne

PostPosted: Tue Jul 17, 2012 3:55 am
Reply with quote

is it not funny, that the answer to most problems seems to be
MORE IRON (even if it is metallic coated plastic in this case).
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Tue Jul 17, 2012 10:50 am
Reply with quote

That's the problem with such errors, they just appear once - and then will vanish by their own.

Just for some more hope - can you please show the SYSIN contents?
Back to top
View user's profile Send private message
socker_dad

Active User


Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA

PostPosted: Wed Jul 18, 2012 6:32 pm
Reply with quote

Code:

SYSIN :                                                     
*************************************************************
* SORT CARD MEMBER IS MAC90500                               
* COPYBOOK MEMBER  IS ACTADL01                               
*************************************************************
 SORT FIELDS=(11,2,CH,A,       AAL-POL-STATE-CODE           
              9,2,CH,A,        AAL-LINE-OF-BUSINESS         
              8,1,CH,A,        AAL-COMPANY-NUMBER           
              13,9,CH,A,       AAL-POL-FILE-NO               
              22,4,CH,A,       AAL-POL-UNIT-NO               
              42,5,CH,A,       AAL-AGENT-NUMBER             
              29,2,PD,A,       AAL-TERRITORY-CODE           
              31,5,PD,A,       AAL-ZIP-CODE                 
              667,3,PD,A,      AAL-ZIP-CODE-LAST4           
              36,2,PD,A,       AAL-COUNTY                   
. . . .
              718,3,CH,A,      AAL-ACCIDENT-DESC
              721,15,CH,A,     AAL-CLAIM-NUM     
              762,10,CH,A),    AAL-LOSS-TYPE-CD 
              SIZE=E2500000,EQUALS               
Back to top
View user's profile Send private message
socker_dad

Active User


Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA

PostPosted: Wed Jul 25, 2012 7:29 pm
Reply with quote

Well it turns out that no one is correct: this is a SyncSort issue for which they have a fix (PTF) that we can only install with an IPL (our next scheduled on is in September).

According to SyncSort: "The Abend066 is not a filesize issue. It’s a timing issue between two concurrent SRBs running and there is a window of opportunity when there are a number of instructions at one time.  It could be related to a data pattern, but I could not say for sure."

So I guess the answer is, when you get an S066 abend, wait 15 to 30 minutes and resubmit the job!

Vendors - you gotta love them (because shooting them is illegal!).
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Wed Jul 25, 2012 8:24 pm
Reply with quote

socker_dad wrote:
Vendors - you gotta love them (because shooting them is illegal!).
LOL - I also loved the phrase "window of opportunity".

Thanks for the follow up though, now if Abend066 is there and SyncSort is involved - I know who to blame upon!
Back to top
View user's profile Send private message
socker_dad

Active User


Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA

PostPosted: Thu Jul 26, 2012 9:24 pm
Reply with quote

If you loved that, you'll love the latest message from SyncSort (I'll leave the reps name off to preserve her dignity):

Quote:

In a JCL sort with no Input Exits, the SIZE and FILSZ parameters are ignored because we can access the actual filesize from SORTIN.


In other words, if you don't have a MODS parameter, coding SIZE= in the Sort control members is a waste of code - it's apparently ignored..... icon_eek.gif
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Fri Jul 27, 2012 11:37 am
Reply with quote

I've not verified it with Manuals, however, keeping in mind what you've said, I'll walk slowly now...
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Fri Jul 27, 2012 7:04 pm
Reply with quote

Hello,

Possibly i've gotten lost.

Quote:
In a JCL sort with no Input Exits, the SIZE and FILSZ parameters are ignored because we can access the actual filesize from SORTIN.
Why might one prefer an estimated value over the "real" value when available? If there is nothing "dynamic" (i.e. user exit(s)) with the run, why should the sort bother with the estimates?
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts Compare only first records of the fil... SYNCSORT 7
No new posts ISAM and abend S03B JCL & VSAM 9
No new posts Abend S0C4 11 (Page Translation Excep... PL/I & Assembler 16
No new posts WER999A - UNSUCCESSFUL SORT 8ED U Ab... SYNCSORT 5
No new posts the system or user abend SF0F R=NULL COBOL Programming 0
Search our Forums:

Back to Top