> We actually want to elliminate this OPNQRYF because it builds the access
> path every time the user selects an option, which also takes a long time.

I can understand this wish. Often OPNQRYF or using SQL is a fast and easy way to
solve a problem but it is a little like a "break section" because of various
reasons. - Who cares.. ;-)

Now: really - I only realize two possibilities for your problem:

(a) creating needed LF to all PF and using "matching records" (yes: although
there are some who hate it ;-), yes: although there are some who find it to be
complicated (it is _not_... it is easier using MR than coding all level
structures by yourself :-) ; btw I only used MR once during my 8 yrs of
programming)

(b) avoiding the "takes a long time" by creating the "right" LFs for the PFs so
that u can presume that the "access path optimizer" of OPNQRYF can join the 
files
as u want them a.s.a.p.

Andreas K., Germany.

+---
| 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 thread ...

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.