Re: I-spec example

[Booth Martin <booth@xxxxxxxxxxxx>]

The solution that is troubling you solves problems where there are 
different record types in the file (very common way back then).  The 
record ID was just to give you a way to operate on the various record 
types that you defined.  For example, lets say your program only wants 
records that are for the state of California.  You could define a record 
type "01" where column X="C" and column X+1 = "A" and all other records 
are ID "99" and then process only "01" records, ignoring all "99" 
records.  You could define various record types for various states and 
set the record type(s) you want to process with external switches.  
ahhh...  I miss the good old days with smell of External Switches in the 
air....

Since that is not a part of your problem, then just ignore the whole 
issue.  Its moot.

James H. H. Lampert wrote:
> Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:
>   
> > I don't understand the question.  I-specs are pretty 
> > much always coded 
> > the same way...  you list the from & to positions of the 
> > field, and you 
> > list the field name.   I'm not understanding what you're 
> > looking for?
> >     
>
> I think I have the "field description entries" down; my 
> problem is understanding the whole "record idenfification 
> entry" business, about which I'm completely clueless.
>
> There's only one kind of record being read.
>
> --
> JHHL
>