View previous topic :: View next topic
Author
Message
santhoshm New User Joined: 13 Jun 2007Posts: 32 Location: chennai
Hi Please suggest me what went wrong with my job.
I am getting an abend of U0016.
Here are the details.
Code:
//SORT EXEC PGM=SORT
//SORTLIB DD DSN=SYSTEM.SORTLIB,DISP=SHR
//SYSOUT DD SYSOUT=*
//SYSLST DD SYSOUT=*
//SORTWK01 DD UNIT=DISK,SPACE=(CYL,(15,2),RLSE)
//SORTIN DD DSN=SMANDAP.INPUT.TEST,DISP=OLD
//SORTOUT DD DSN=SMANDAP.OUTPUT.TEST,DISP=(NEW,CATLG,DELETE),
// DCB=(RECFM=FB,LRECL=100,BLKSIZE=1900),
// SPACE=(CYL,(15,2),RLSE),UNIT=DISK
//SYSIN DD *
SORT FIELDS=(15,9,A,24,2,A,13,1,A,31,2,A,82,3,A,37,3,A,9,4,A,91,4,A,
28,3,A,71,1,A,7,2,A,26,2,A),
FORMAT=CH
SUM FIELDS=(73,09,ZD)
//*
And the messages are
Code:
SYSIN :
SORT FIELDS=(15,9,A,24,2,A,13,1,A,31,2,A,82,3,A,37,3,A,9,4,A,91,4,A,
28,3,A,71,1,A,7,2,A,26,2,A),
FORMAT=CH
SUM FIELDS=(73,09,ZD)
WER276B SYSDIAG= 4160, 77275, 77275, 366399
WER164B 6,044K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,
WER164B 0 BYTES RESERVE REQUESTED, 5,272K BYTES USED
WER146B 20K BYTES OF EMERGENCY SPACE ALLOCATED
WER108I SORTIN : RECFM=FB ; LRECL= 100; BLKSIZE= 6400
WER110I SORTOUT : RECFM=FB ; LRECL= 100; BLKSIZE= 1900
WER410B 5,016K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,
WER410B 0 BYTES RESERVE REQUESTED, 5,016K BYTES USED
WER036B G=24256
WER177I TURNAROUND SORT PERFORMED
WER045C END SORT PHASE
WER055I INSERT 0, DELETE 19222
WER211B SYNCSMF CALLED BY SYNCSORT; RC=0000
WER049A SUM FIELD OVERFLOW
Back to top
expat Global Moderator Joined: 14 Mar 2007Posts: 8796 Location: Welsh Wales
Where does it say that it abended U0016 ?
Are you sure it was this step that abended ?
Back to top
santhoshm New User Joined: 13 Jun 2007Posts: 32 Location: chennai
Yes I'm Sure.
See the following message that I got.
Code:
SORT - COMPLETION CODE - SYSTEM=000 USER=0016 REASON=00000000
Back to top
Bitneuker CICS Moderator Joined: 07 Nov 2005Posts: 1104 Location: The Netherlands at Hole 19
Long ago I used to have a U0016 often and mostly a wrong recordlength was the cause.
Back to top
Bitneuker CICS Moderator Joined: 07 Nov 2005Posts: 1104 Location: The Netherlands at Hole 19
But this one could be because of the following:
Quote:
Code:
WER049A SUM FIELD OVERFLOW
Back to top
William Thompson Global Moderator Joined: 18 Nov 2006Posts: 3156 Location: Tucson AZ
Simple:
WER049A SUM FIELD OVERFLOW
Back to top
enrico-sorichetti Superior Member Joined: 14 Mar 2007Posts: 10889 Location: italy
I am no syncsort expert, just a good reader of posts...
the last line of Your output says
Quote:
WER049A SUM FIELD OVERFLOW
worth investigating
regards
e.s
Back to top
Bitneuker CICS Moderator Joined: 07 Nov 2005Posts: 1104 Location: The Netherlands at Hole 19
William Thompson wrote:
Simple:
WER049A SUM FIELD OVERFLOW
Beat ya
Back to top
Bitneuker CICS Moderator Joined: 07 Nov 2005Posts: 1104 Location: The Netherlands at Hole 19
enrico-sorichetti wrote:
I am no syncsort expert, just a good reader of posts...
the last line of Your output says
Quote:
WER049A SUM FIELD OVERFLOW
worth investigating
regards
e.s
Beat you too
Back to top
CICS Guy Senior Member Joined: 18 Jul 2007Posts: 2146 Location: At my coffee table
Bitneuker wrote:
William Thompson wrote:
Simple:
WER049A SUM FIELD OVERFLOW
Beat ya
Ha! It took you two replies.....Wat's a'matta, missed it the first time....giggle....
Back to top
Gautam512 Active User Joined: 05 Oct 2005Posts: 308 Location: Vizag / US
hi,
can you tell what is the record length of the file on which you are doing the sort..
Back to top
krisprems Active Member Joined: 27 Nov 2006Posts: 649 Location: India
santhoshm
Code:
WER049A SUM FIELD OVERFLOW
To avoid overflow, you need to incresse the length of the field that you are summing using the INREC option and then SUM them up.
Note: this may end up in increasing your o/p file length.
Back to top
murmohk1 Senior Member Joined: 29 Jun 2006Posts: 1436 Location: Bangalore,India
OR
make sure that your SUM value never crosses 999,999,999.
Back to top
skkp2006 New User Joined: 14 Jul 2006Posts: 93 Location: Chennai,India
From the manuals......
If arithmetic overflow or underflow occurs during the summing of two records, those
records are not summarized and neither record is deleted. Further processing is
determined by the option selected at installation through the SUMOVFL parameter or
the run time parameter OVFLO. If the RC16 option of this parameter has been
selected, processing will terminate with a WER049A critical error. For the RC0 (the
delivered default) or the RC4 option, sum processing will continue and a WER049I
message will be issued (only for the first occurrence). If a subsequent pair of records
with equal control fields can be summarized without causing overflow or underflow,
they will be summarized. To avoid arithmetic overflow, use the INREC control
statement to insert zeros of the proper format immediately before the sum field. For
example, for a PD field, use nZ to insert binary zeros.
Back to top
Please enable JavaScript!