|
Alan,I don't think one can create a logical over a logical. Leastwise, I've never seen such a thing.
You can create a logical over multiple physicals by simply defining multiple PFILE(x/x) statements in your DDS. I've done this several times with history labels such as you describe (Header and Detail). But it was always one logical over the header tables; a separate logical over the Details. Never tried to combine them into a multi-file join, but using this as a starting place you might try it to see how/if it works.
You, also, have the same "problem" that I have. That is, the PF's are in multiple libraries. My rule is: The logicals go into the same library as the physical. In this scenario this won't work and the libraries have to be specified in the PFILE( ) statement rather than relying upon the library list to keep things straight.
* Jerry C. Adams *IBM System i Programmer/Analyst B&W Wholesale Distributors, Inc.* * voice 615.995.7024 fax 615.995.1201 email jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> Alan Shore wrote:
Hi everybody. I have a question concerning the concatenation of data from multiple files, but from different libraries. I have 4 pair of files, each pair consists of a HDR and a DTL file, with a one to many correlation, for example:- LIBRARY1/HDRA & LIBRARY1/DTLA LIBRARY2/HDRB & LIBRARY2/DTLB LIBRARY3/HDRC & LIBRARY3/DTLC LIBRARY4/HDRD & LIBRARY4/DTLD A join logical can be built over each of these files, for example LIBRARY1/HDRADTLA LIBRARY2/HDRBDTLB LIBRARY3/HDRCDTLC LIBRARY4/HDRDDTLD each of these HDR files has the same DDS layout as the other HDR files each of these DTL files has the same DDS layout as the other DTL files each of the join logicals has the same DDS layout as the other join logical files My question is:- is there a way to create ONE logical from these four join logical files? Thanks in advance
As an Amazon Associate we earn from qualifying purchases.
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.