|
Stefan, thank you for the reply. I tried this and must have done it wrong. I got a 9-digit relative record number in a 7-record file. Where in the INFDS does one look for the rrn? One other thing (of many) that I don't understand is: is the relative record number always the rrn of the record in it's physical file? The logical file won't establish it's own rrn, based upon it's sequencing and omit/includes?? In <412566E7.002D4916.00@sundsvall3.notes.sema.se>, on 12/27/98 at 09:20 AM, stefan.tageson@notes.sema.se said: >One way to do it might be to specify an INFDS for the LF and save the >rel.rcd.nbr in a hidden field in the subfile. Then use the PF to chain by >rrn (Don't specify keyed access on the F-spec). As a bonus you will get >the fastest possible random record retrieval. >// Stefan Tageson >+>----------------------------------------------------------------------<+ > tel: +46 40 693 3500 > fax: +46 40 693 3600 > mobile: +46 708 51 3543 > e-mail stefan.tageson@notes.sema.se >+>---------------------------------------------------------------------<+ >boothm@ibm.net on 98-12-27 05:24:31 >Please respond to MIDRANGE-L@midrange.com > > > > To: MIDRANGE-L@midrange.com > > cc: (bcc: Stefan Tageson/MMX/Sema Group/SE) > > > > Subject: Relative record number > >I have four files: > FileF is an unkeyed name & address physical file. > FileFL1 is a logical over FileF based upon first name. > FileFL2 is a logical over FileF based upon last name > FileFL3 is a logical over FileF based upon phone number >I wish to display any one of the three logical files as subfiles to the >user depending upon the user's choice. While the files are in order >there is no assurance that there is a unique key in any of the three >logical files. >In the past I would have generated a unique number and created a new >field for the ID number to act as a unique key for the file set. Now >though I am wondering if there is a better way, for instance Relative >Record number? And if so, how is it implemented in this situation? >-- >----------------------------------------------------------- >boothm@ibm.net >Booth Martin >----------------------------------------------------------- >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to >MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: >david@midrange.com >+--- >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- -- ----------------------------------------------------------- boothm@ibm.net Booth Martin ----------------------------------------------------------- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
