× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Keying Program Described Files
  • From: ericadelong@xxxxxxxx
  • Date: Tue, 21 Apr 98 12:08:41 -0500


Ramesh, 

Yes, I believe that you _DO_ need contiguous fields to build an access path for 
a non-described file. There are several possibilities that could work for you. 
IMO, creating DDS for the file would be best. However, the following could be 
made to work (but it's a work-around by almost all standards).

1) move file to QS36F

2) use STRS36PRC (in CLP) to issue the S/36 command BLDINDEX specifying the 
locations and length of your composite key fields.

3) the resulting file will contain the record image with the composite key data 
appended to the end of the record that is then used to key the file.

So, if you have a 80 byte record and want to key off two 4 byte fields, the 
resulting file will be 1-80 original record, 81-84 CKey1, 85-88 CKey2. Your 
composite key is actually treated as a single 8 byte alpha key.

Not very pretty, but it will work.

Eric A DeLong
ericadelong@pmsc.com

______________________________ Reply Separator _________________________________
     
     
Hi,
     
Is it necessary that parts of Composite Key used to Key a Indexed Program 
Described File should be contigious in the record.
RPG/400 User manual Topic- 7.2.1.1 says it should be continous.
But we feel it is not necessary that Parts of Key should be continous in 
record even for Program Described Files.
     
     
Is there any way to Key a Program Described Flat File without creating 
External DDS.
     
     
Thanx in advance                        
     
Regards,
Ramesh


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.