×
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.
On 01-Apr-2014 15:09 -0700, Chris Bipes wrote:
<<SNIP>> I want to define a standard and move in that direction to
avoid library list issues in the future. <<SNIP>>
There are several "client" special registers available to the SQL at
the server, from values that can be established by the client; e.g. the
Client Application Name via CURRENT CLIENT_APPLNAME
A stored procedure invoked by an application [or possibly invoked via
an exit instead, if SQL is allowed and does not impair the SQL that
would run in the connection and the library list was already established
for the connection at that exit point] could establish the library list
according to the application name.
<
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/db2/rbafzspecreg.htm>
IBM i 7.1 Information Center -> Database -> Reference -> SQL reference
-> Language elements
_Special registers_
"A special register is a storage area that is defined for an application
process by database manager and is used to store information that can be
referenced in SQL statements.
...
CURRENT CLIENT_APPLNAME
The CURRENT CLIENT_APPLNAME special register specifies a VARCHAR(255)
value that contains the value of the application name from the client
information specified for the current connection.
..."
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
