RE: Quick question for the RPG Cycle experts (if there are any left)

Yes, using CL to pre-position the primary file, before calling the RPG program, 
does work indeed, because I have used it. For non-keyed primary files, the 
first, and for the keyed files, the second example: 

OVRDBF FILE(A) POSITION(*RRN 100)

OVRDBF FILE(A) POSITION(*KEY 1 A '0123')

That's what I would use. The record address file would require a file of record 
numbers and special values inside the F-specs, and the limits file would 
require the same thing. Simplest is if you can just put the above CL in front 
of the RPG. 

..As I'm typing I remembered a file type we used in the S/34 and

occasionally on the S/36.  It's a record address type file IIRC.  You
create a record with from and to keys and the program only reads those
records from an associated data file.  I haven't used one in over 10
years and don't remember how to code it but it might be worth a look...Rick

I think Rick described a "limits" file, or "set limits file", or something like 
that. You create a file in which each record has from-to key values, and then 
in your F-specs you did something like use it as a primary file, with some kind 
of keyword value that pointed its effect to the other file name. Whew..

The record address file was/is a file produced from sort specs (G-specs I think 
they were/are), in which said file was simply a list of record addresses for 
the actual data records. It served as the primary file again, but used a 
keyword to name the actual data file. 

The command FMTDTA I think produces one or another of this kind of file. 

Maybe instead of a keyword it was E-specs. Been a long time... 

--Alan