AppInfo (APP) connection parameter

Assists administrators in identifying the origin of particular client connections from a database server.

Syntax

{ AppInfo | APP }=keyword=value

Allowed values

Clients can specify their own string that is appended to the generated string. The AppInfo property string is a sequence of semicolon-delimited key=value pairs. The valid keys are as follows:

API DBLIB, ODBC, OLEDB, ADO.NET, iAnywhereJDBC, PHP, PerlDBD, or DBEXPRESS.
APPINFO If you specified AppInfo in the connection string, the string entered.
EXE The name of the client executable (Windows, Linux, and Solaris).
HOST The host name of the client computer.
IP The IP address of the client computer.
OS The operating system name and version number (for example, Windows XP).
OSUSER The operating system user name associated with the client process. If the client process is impersonating another user (or the set ID bit is set on Unix), the impersonated user name is returned. An empty string is returned for version 10.0.1 and earlier clients, and for HTTP and TDS clients.
PID The process ID of the client (Windows and Unix only).
THREAD The thread ID of the client (Windows and Unix only).
TIMEZONEADJUSTMENT The number of minutes that must be added to the Coordinated Universal Time (UTC) to display time local to the connection.
VERSION The version of the client library in use, including major and minor values, and a build number (for example 12.0.0.2413).

This connection parameter is sent to the database server from embedded SQL, ODBC, OLE DB, or ADO.NET clients and from applications using the SQL Anywhere JDBC driver. It is not available from Sybase Open Client or jConnect applications.

It consists of a generated string that holds information about the client process, such as the IP address of the client computer, the operating system it is running on, and so on. The string is associated in the database server with the connection, and you can retrieve it using the following statement:

SELECT CONNECTION_PROPERTY( 'AppInfo' );

If you specify a debug log file in your client connection parameters, the AppInfo string is added to the file.

Example

Connect to the sample database from Interactive SQL (the SQL Anywhere JDBC driver is used by default):

dbisql -c "UID=DBA;PWD=sql;DBF=samples-dir\demo.db"

View the application information:

SELECT CONNECTION_PROPERTY( 'AppInfo' );

The result is as follows (in a single string):

IP=ip-address;
HOST=computer-name;
OSUSER=user-name;
OS='Windows XP Build 2600 Service Pack 2';
EXE='C:\Program Files\SQL Anywhere 12\Bin32\dbisql.exe';P
ID=0xcac;
THREAD=0xca8;VERSION=12.0.0.2413;
API=iAnywhereJDBC;
TIMEZONEADJUSTMENT=-240

Connect to the sample database from Interactive SQL, appending your own information to the AppInfo property:

dbisql -c "UID=DBA;PWD=sql;DBF=samples-dir\demo.db;APP=Interactive SQL connection"

View the application information:

SELECT CONNECTION_PROPERTY( 'AppInfo' );

The result is as follows (in a single string):

IP=ip-address;
HOST=computer-name;
OSUSER=user-name;
OS=Windows XP Build 2600 Service Pack 2;
EXE=C:\Program Files\SQL Anywhere 12\Bin32\dbisql.exe;
PID=0xcac;
THREAD=0xba8;
VERSION=12.0.0.2413;
API=iAnywhereJDBC;
TIMEZONEADJUSTMENT=-240;
APPINFO='Interactive SQL connection'

Discuss this page in DocCommentXchange.