I have a file which is of 958 bytes. The file has junk values in some fields, due to which the SUM fileds done on these fields was giving S0C7. So I used INREC to overlay these fields with 0 (these fields are PD). But still the job is failing with S0C7.
220,3,PD,A,
288,1,CH,A,
484,2,CH,A,
493,9,PD,A,
634,1,ZD,A)
*
SUM FIELDS=(39,9,PD,
540,9,PD)
If I split this into 2 different Steps, first step contains the INREC and INCLUDE and the second step contains the SORT and SUM fields the job is running fine with expected output.
I also used ICETOOL to verify the output after INREC and there is no discrepancies shown and the job runs fine. Below is the ICETOOL Sort Card.
Code:
COPY FROM(SORTIN) TO(T1) USING(CTL1) -> CTL1 contains the INREC and INCLUDE statments
VERIFY FROM(T1) ON(540,9,PD) -> To verfiy if the fields used for SUM fields are having proper values.
VERIFY FROM(T1) ON(039,9,PD) -> To verfiy if the fields used for SUM fields are having proper values.
SORT FROM(T1) TO(SORTOUT) USING(CTL2) -> Contains the SORT and SUM fields statement.
Could you please help me on what is wrong with the first SORT Card. Do I need to use 2 steps to achieve the purpose?
Note: - I cannot omit the records which are having junk values.
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
I can't see matching brackets on your INCLUDE=.
I think your problem is the things aren't working in the order you expect. Have you considered using INCLUDE/OMIT COND=, which operates before INREC? You are using INCLUDE= on OUTFIL, which is after INREC, SORT, SUM, OUTREC.
When you split into two steps, your INCLUDE was done before the SORT/SUM. With the single step it was done after the SORT/SUM.
So no, there is no reason to split things up. And no reason to read the file four times in ICETOOL.
It was a typo. My code has an ending brackets in the INCLUDE.
I did try the INCLUDE COND before the INREC. But the problem is I need to overlay 19 '9' from position 4 in case if the 1st 3 positions are 999 (currently the field contains spaces). If I don't do this, the INCLUDE COND will actually skip the record (as shown below).
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
Can you frame the INCLUDE so that it also gets the records you are going to amend in the INREC?
If not, perhaps forget the SUM and look at OUTFIL reporting features. You'll need REMOVECC,NODETAIL and TRAILER2 with TOT for the fields you are currently SUMming.
Bear in mind that SUM will base on the first record being SUMmed (see discussion of EQUALS/NOEQUALS in the manual) and TRAILER2 on the last (bear in mind same discussion).
Code:
INCLUDE/OMIT COND=
INREC
SORT/MERGE
SUM
OUTREC
OUTFIL(s) with INCLUDE=/OMIT= (optional)
Remember that in whatever order you code them, this is the order they are going to be processed in. Trying to use INCLUDE=/OMIT= to modify SUM values will not work.
Thanks Bill for your suggestion. I modfied the SORT to have INCLUDE before the INREC and used an OMIT in OUTFIL. The got the results as expected. Below is the SORT Card.
