• Subject: RE: Problem with reading a file that does have keys
  • From: "Burrows, Thomas 1001" <Burrows.Thomas@xxxxxxxxxxxxxx>
  • Date: Tue, 23 Oct 2018 20:25:08 +0000
  • List-archive: <https://archive.midrange.com/rpg400-l/>
  • List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
  • List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
  • List-post: <mailto:rpg400-l@midrange.com>
  • List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
  • List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>
  • Msip_labels: MSIP_Label_be4b3411-284d-4d31-bd4f-bc13ef7f1fd6_Enabled=True; MSIP_Label_be4b3411-284d-4d31-bd4f-bc13ef7f1fd6_SiteId=63ce7d59-2f3e-42cd-a8cc-be764cff5eb6; MSIP_Label_be4b3411-284d-4d31-bd4f-bc13ef7f1fd6_Owner=thomas.burrows@xxxxxxxxxxxxxx; MSIP_Label_be4b3411-284d-4d31-bd4f-bc13ef7f1fd6_SetDate=2018-10-23T20:25:04.2612320Z; MSIP_Label_be4b3411-284d-4d31-bd4f-bc13ef7f1fd6_Name=Internal; MSIP_Label_be4b3411-284d-4d31-bd4f-bc13ef7f1fd6_Application=Microsoft Azure Information Protection; MSIP_Label_be4b3411-284d-4d31-bd4f-bc13ef7f1fd6_Extended_MSFT_Method=Automatic; MSIP_Label_a0819fa7-4367-4500-ba88-dd630d977609_Enabled=True; MSIP_Label_a0819fa7-4367-4500-ba88-dd630d977609_SiteId=63ce7d59-2f3e-42cd-a8cc-be764cff5eb6; MSIP_Label_a0819fa7-4367-4500-ba88-dd630d977609_Owner=thomas.burrows@xxxxxxxxxxxxxx; MSIP_Label_a0819fa7-4367-4500-ba88-dd630d977609_SetDate=2018-10-23T20:25:04.2612320Z; MSIP_Label_a0819fa7-4367-4500-ba88-dd630d977609_Name=Companywide usage; MSIP_Label_a0819fa7-4367-4500-ba88-dd630d977609_Application=Microsoft Azure Information Protection; MSIP_Label_a0819fa7-4367-4500-ba88-dd630d977609_Parent=be4b3411-284d-4d31-bd4f-bc13ef7f1fd6; MSIP_Label_a0819fa7-4367-4500-ba88-dd630d977609_Extended_MSFT_Method=Automatic; Sensitivity=Internal Companywide usage

Peter:

I had the "K" in column 34. Removed that and took out the SETLL. Get the exact same results. At no time should
This statement be TRUE;

read arlcu;
if cunano = savcuno;
count4 = count4 + 1;
endif;

savcuno = cunano;
count1 = count1 + 1;

================

There are 36,815 records in ARLCU and not a single repeating CUNANO.

Not sure what is up.

Thomas





-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxx> On Behalf Of Peter Dow
Sent: Tuesday, October 23, 2018 2:55 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Problem with reading a file that does have keys

[ External Email ]

----------------------------------------------------------------------
Hi Thomas,

In regards to your question "is there anything on the F specs I could be overlooking?", make sure there's a "K" in pos.34 of the F-spec, or if you're doing free-format, the KEYED keyword. Otherwise you'd be reading the file by RRN instead of by key.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /


On 10/23/2018 8:45 AM, Thomas Burrows wrote:
I want to read a keyed file from top to bottom. i.e. I am finding that I
seem to read some records more than once.

is there anything on the F specs I could be overlooking?
I put a counter in for the read and I get the right number of times through
the read routine.

Doing a "DOU NOT %EOF(filename)
Then an EXSR X1 to the read routine where the read on the file is
BEGSR x1
READ FILENAME;
endsr

I put an if statement in after the read looking against one of the account
numbers that is only in the file being read from once. But I get SEVEN or
more hits in the IF statement checking against that one account number.

Thomas Burrows


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].