Re: Three part names and library lists

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

The issue in this specific use case is just a query.  The trick is that 
files for this application may reside in one of several libraries.  With 
a library list, I can simply do "select * from FILE1 join FILE2 ..." 
rather than "select * from PROD.LIB1.FILE1 join PROD.LIB2.FILE2".  In 
the former I don't even have to specify the schema.  I was asking if 
there is a syntax for three-part naming that allows you to not specify 
the schema, which I understand is somewhat oxymoronic, but I was just 
wondering if there was some sort of PROD.*LIBL.FILE1 syntax.

On 4/14/2021 6:24 AM, Rob Berendt wrote:
> Is this application supposed to rely upon library lists on both the local and remote systems?  For example, post data from the inventory balances from a remote plant into the inventory balances on the central system?
>
> If so you may have to replicate the logic used to determine the persons library list on the remote system.  Whether it be from the job description, an initial library list data area, etc.
> Then you could use object_statistics to find libraries within that list which contain the desired file. (finding the 'first' library will be fun).  Then dynamically prepare your 3 part naming statement.
>
> Rob Berendt