× 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.



Hello  Peter,

I do not completely understand your request, but I give it a shot:

Records with the same key value will be processed in arrival sequence, thus 
defining one filed on the KEYFIELD parameter can be used.

If you want to process data in the arrival sequence of one of those key fields, 
then create a LF and include only the fields you need for processing, define no 
key. No need for OPNQRYF there.

And last, but not least: perhaps the good, old RPG cycle can help out here.

Regards.
Carel Teijgeler

======= At 2002-08-09, 10:54:00 you wrote: =======

>we have a tricky problem presented to us.
>
>We have a physical file with the following key fields:
>
>Key field 1 : float number
>Key field 2 : float line number
>
>The idea is to process this file for one single float, but on arrival
>sequence.
>
>Is it possible to do this with OPNQRYF?
>
>I looked at the possible options for the KEYFLD parameter, but I don't
>think they can do what we want:
>
>*FILE will use the combined key that we do not want to follow;
>*NONE may or may not give the desired result ('It is even possible for the
>system to give query records in a different arrangement if the same query
>is run twice, based on such factors as the current number of records in the
>file members queried' according to on-line help);
>
>Can I do a select (QRYRSLT parameter) and specify the rrn as key field?

= = = = = = = = = = = = = = = = = = = =







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.