×
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.
Thank you. I may use that when my workaround doesn't work. Like for things like functions which may not be supported by an alias.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Bryan Dietz
Sent: Friday, February 1, 2019 10:10 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: sql, Using a variable or column name on a 'connect to'
This is on a similar track, but I found this Twitter from Scott F.
that is along similar lines as the "connect to"
Hey, #SQL #Db2fori users...
If you code a table based 3-part name in your WHERE clause, your UDTF invocation will execute on the target RDB.
-- Example:
select current_server, h.* from table(qsys2.history_log_info()) h where exists (select 1 from rmtdb.sysibm.sysdummy1);
maybe it helps or spurs additional thought.
Bryan
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: sql, Using a variable or column name on a 'connect to', (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.