Database environment variables
With Lycia, you can work with several databases including Informix, Oracle, SQL Server, etc.
Applications connecting to a database use a database driver that, in its turn, uses a database client software. The database client software usually needs specific configuration that is accomplished by setting the necessary environment variables. Database environment variables define information such as installation directory of the client software and localization settings.
This chapter describes basic environment variables used and/or required for database connection.
For example, when connecting to an Informix database, you must set these environment variables in inet.env.
LOGNAME =
INFORMIXPASS =
LYCIA_DB_DRIVER = informix
INFORMIXDIR = C:\Program Files\IBM Informix Client SDK
INFORMIXSERVER = querix_tcp
CLIENT_LOCALE = en_us.UTF8
DB_LOCALE = en_us.UTF8
Specifies the language, territory, and code set that the client application uses in I/O operations, end user formats, and processing ESQL statements:
CLIENT_LOCALE = fr_ca.8859-1
Possible values and their meaning:
<language>_<territory>.<code_set>@modifier
Specifies how dates are displayed on the client side:
DBDATE=MDY4/ (default)
Possible values and their meaning:
D and M for day and month
Y2 and Y4 for year and year precision
- . /0 for separators
Specifies the symbol that separates loaded and unloaded files in the LOAD and UNLOAD statements:
DBDELIMITER=|
Possible values and their meaning:
any character except for {0-9, a-f, A-F, \}
Specifies the Informix database locale, which the Informix database server uses to process locale-sensitive data:
DB_LOCALE = fr_ca.8859-1
Possible values and their meaning:
<language>_<territory>.<code_set>@modifier
Specifies the paths for directories that contain the DB-Schema files.
DB_SCHEMA = /home/informix/workdir/projects/debugger
You can provide several paths, using a colon (:) separator (Linux/UNIX) or a semicolon (;) (Windows).
Possible values and their meaning:
<path>
Specifies the directory that contains sub-directories in which your Informix® product files are installed:
INFORMIXDIR = /opt/IBM/informix
Possible values and their meaning:
<directory_path>
Specifies the password valid on Informix database server.
INFORMIXPASS = password-123
Possible values and their meaning:
{any set of symbols and/or characters}
Specifies the default database server to which an explicit or implicit connection is made by an SQL API client, the DB-Access utility, or another IBM® Informix® product:
export INFORMIXSERVER = dbserver_main
Possible values and their meaning:
{dbservername}
Stores the path to the SQLHOSTS.STD file, which, in turn, stores connectivity information for the Informix® DB Server.
INFORMIXSQLHOSTS = /opt/IBM/informix/etc/
By default, the SQLHOSTS.STD file is located in the following directories:
Specifies the user name valid on Informix database server:
LOGNAME=informix
Possible values and their meaning:
{string}
Specifies the default database driver that will be used at runtime:
LYCIA_DB_DRIVER = informix (default)
Possible values and their meaning:
{informix, odbc, oracle}
Specifies the path to search for Lycia libraries:
Possible values and their meaning:
<path to folder>
Specifies the full path to the the odbc.ini file:
ODBCINI = /etc/odbc.ini
Possible values and their meaning:
<file_path>
Specifies the base ODBC connection string for the database connection:
ODBC_DSN=DSN=mysql;USER=informix;Password=123456;Database=dbname
Possible values and their meaning:
{DSN name}
Specifies the directory, where your Oracle® product is installed:
ORACLE_HOME = C:\ORACLE\instantclient_ver._No
Possible values and their meaning:
<directory_path>
Specifies the default server instance for current connection:
ORACLE_SID = querix_ora
Possible values and their meaning:
{server_instance}
Controls the type of DB-Schema file loading.
QX_LOAD_ENTIRE_SCHEMA = false
Possible values and their meaning:
{true, false}
If set to false (default), the Schema file is loaded using the ‘lazy loading’. If set to true, the compiler loads the entire DB-Schema.
The lazy loading of DB-Schema is a type of parsing, during which the compiler parses the Schema until the required entity is found. After that, the parsing stops, and if it is then resumed, the schema is parsed further from where the previous parsing has stopped.
Controls whether the compiler should search for DB-Schema at compilation.
QX_USE_DB_SCHEMA_FILE = true
Possible values and their meaning:
{true, false}
If true (default), the compiler will search for the DB-Schema first, then try to connect to DB server if the file was not found.
If false, this variable forces a connection to the database instead of loading the DB-Schema file at compilation.
Specifies path to the directory which contains dbtrans file on UNIX:
QXTRANS=$ORACLE_HOME/sqldeveloper/ide
The dbtrans configuration file contains mappings from database names used in 4GL code (for example, DATABASE <dbname>) to an Oracle® user logon string.
Possible values and their meaning:
<directory_path>
Specifies the directory containing the Oracle Net Services configuration files:
TNS_ADMIN = $ORACLE_HOME/network/admin
Possible values and their meaning:
<directory_path>