After some private emails, files and job output, Sri noticed that some of
the sum fields where too small to host the accumulated values generated by
the sort sum statement.
Fixed that and it as expected.
Tx to Sri and others that suggested solutions. The original code was in
different language tr
use an inrec statement to enlarge numeric fields so you don't exceed
the size of the field.
On Sun, Oct 27, 2019 at 7:08 AM ITschak Mugzach wrote:
>
> Sri,
>
> This was just an example. I am trying to summarize by sort keys. there
> might be ten records with same sort keys. I expect a single reco
>>Can send you the file and job so you can see
> yourself ). please confirm this option.
Please send as text files. I would also like to see your joblog too.
Thanks.
Kolusu
DFSORT Development
IBM Corporation
--
For IBM-MAIN su
Yes.
I am running a batch version. Can send you the file and job so you can see
yourself ). please confirm this option.
The statements are as in my sample. I would expect a single combination for
sort keys summarised in sortout.
בתאריך יום א׳, 27 באוק׳ 2019, 14:31, מאת Sri h Kolusu :
> >>> Mo
>>> More specific:
> OPTION EQUALS
> SORT FIELDS=(6,5,ch,a,53,3,ch,a)
> sum fields=(245,15,ZD,123,11,ZD)
>
> As the are about 15 records with same sort keys I want to summarize all
> into a single record. Is this possible, or should I write my own program?
ITschak,
That should be easily summed.
Sri,
This was just an example. I am trying to summarize by sort keys. there
might be ten records with same sort keys. I expect a single record in
output file (such as DUPKEYS SUM in syncsort). However, the result is that
I get several records with same keys in the output.
More specific:
OPTION E
>>>sum flelds =(3,4,zd,5,6,zd).
ITschak,
I am pretty sure that would result in overlapping error as your summing
field at position 3 for 4 bytes extend up to position 6, but your second
sum field starts at position 5 which overlaps the first sum field. You
should be getting an ICE125A message.
