If the columns are the same, I'd think a UNION would probably do what
you want.
jamesl@xxxxxxxxxxxxxxxxx 10/22/2008 5:48:37 PM >>>
A scenario:
We have a standard *PGM that does lookup operations (via SQL CLI) on
any
arbitrary PF. It's called by our app when "lookup" parameters are
specified in the definition of a data field, and it can be used to
populate associated fields with the returned value. For example, if we
pass it a part number, we can validate the part number, and populate
description, price, and core deposit fields.
We have a customer that has three different files (in different
libraries, but probably with the same name) with part number data. At
this point, we don't know if they're identical, or overlapping, or if
there's a subset/superset relationship, or even if a given part number
means the same thing in all part number files in which it appears.
Assuming we at least don't have the nightmare of part numbers meaning
one thing in one library, and something else in another library, is
there something I can do that will make all three appear as one to SQL?
Thoughts of multi-format logicals spring to mind.
As an Amazon Associate we earn from qualifying purchases.