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



If you look at the same physical file via RUNQRY N file_name(LF) then F4, via a variety of different logical files, it displays the data in the logical sequence of the LF's definition of what is the keys. That is how it works in BPCS where the physical file is NOT indexed, just a collection of data, using different logical definitions of what to include and what is the key sequence.

Keys and Key sequence being defined by the logical file.

I have no idea what would happen if the physical file itself is indexed.
When I look at the physical data via RUNQRY N then name of physical file, I get the helter skelter sequence of how the data was originally added to the file.

You better off using a query definition to dictate sequence.

Can "RUNQRY *N SomeLF" be displayed in key  sequence?

Is it somehow possible to use the runqry command against a logical file
and have the records displayed in key  sequence?

--
-----------------------------------
Booth Martin
http://martinvt.com
-----------------------------------
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.