RE: Record Number / RPG cycle

Maybe I can be officially included in the "old geezer" section for this
reply ... if you define your file as input, primary and don't specify key,
just set up a counter as the cycle processes the file sequentially and
you've got yourself the record number in ascending sequence.  Without using
the cycle,  an alternative method is to use the file information data
structure (binary 397 - 400) for the relative record number.  This method
would probably force most of us to get out the manuals for the INFDS layout.
It's a matter of choice but let's not get rid of the cycle without coming up
with a new name for RPG.  Suggestions for a new name anyone?

-----Original Message-----
From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
Behalf Of Jim Langston
Sent: Wednesday, February 16, 2000 1:16 PM
To: RPG400-L@midrange.com
Subject: Record Number


I am searching through a file for some strings, and I need to find out
what the record numbers are.  I am opening the file Input, Full Procedural,
externally described, and as I understand it, this uses sequential
processing,
that is, record numbers.

Once I find my string, how do I find out what record number I am actually
on?  Until I find out I am going to just increment a counter and hope it's
right, but as we all know, deleted records mess this up.

Thanks.

Regards,

Jim Langston

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---