Re: Relative Record Numbers (RRN)

[Ken Sims <mdrg5003@xxxxxxxxxxx>]

Hi Alfred -

> I work in a JDE environment where most of the tables lack a single
> column I can key queries off of. I find myself having to join multiple
> files and key against multiple fields to get to one buried record buried
> that my user wants to consider changing. My interface is web based and
> if they decide to change the value I'd like to update against the
> relevant RRN instead of dealing with a multi-field where clause of some
> type.
>
> Would anyone like to share real world pros and cons regarding using RRN
> in a similar manner?

I have a program which updates by RRN.  It's just one file, not a 
multi-file situation like yours.  There is no unique key.  The user picks 
the record to be updated through a subfile.  As the program came originally 
from the vendor, it would always update the first record with the matching 
key list, which would not necessarily be the correct record.

I changed the program to save the RRN of each record in the subfile record 
and I use that to update the file.

The RRN is only used within the one transaction and no RGZPFM is going to 
take place while the file is open and in use.  (I control all of the 
reorganizations anyway.)  The only issue would be if the file were 
REUSEDLT(*YES) where the record would be deleted and a new record added at 
that same RRN.  But the file is NOT REUSEDLT(*YES) (and records are only 
deleted once a year during a purge process anyway) so that's not an issue.

Ken
http://www.kensims.net/
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.