×
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.
Actually RPG can not create an LF, DDS nor SQL, no matter :-Q so
discounting the SQL UNION VIEW seems unfounded. Other than the SQL long
name, which can easily be replaced by a short name, there is nothing
that should preclude the file from use in/by RPG.? The RCDFMT clause
added to the CREATE could make it even easier to refer to the VIEW.
And if the concern is for lack of a key, then OPNQRYF KEYFLD() can
generate the key; compile against a keyed PF with the keys generated.
Or... I can stop already, being somewhat facetious, and just offer up
a DDS MFLF source :-) :
<code>
* Files BP1-BP4 are all same PF format; in fact
* each is: CRTDUPOBJ BPA MYLIB *FILE BP# BP# DATA(*YES)
* ;; where the PF source, for example, might be:
* R BPR
* B 9B 0
* P 12 2
* OTHERS xxTyy
*
A R BPR PFILE(BP1/BP1 +
A BP2/BP2 +
A BP3/BP3 +
A BP4/BP4 )
A K B
A K P
</code>
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Logical File over identical files in separate libraries., (continued)
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
