Defining DB2 environment variables
For UNIX and Microsoft Windows operating systems, you must define the following environment variables:
DB2INSTANCE and DB2DIR
Define these variables to connect to a DB2 instance. DB2INSTANCE specifies the instance name, and DB2DIR is the path to the DB2 client installation.
DB2CODEPAGE
DB2CODEPAGE is a DB2-specific environment variable. For Windows and UNIX, Actuate uses DB2CODEPAGE to determine the DB2 database’s client locale. On Windows systems, DB2CODEPAGE is a registry setting. On UNIX systems, DB2CODEPAGE is an environment variable. At execution time when Actuate connects to a DB2 data source, the active code page is in effect for the duration of the connection. All data is interpreted based on this code page. If this variable is not set, Actuate’s DBMS module determines the client locale setting from the operating system locale.
Use db2set to set DB2CODEPAGE. For example, the following command sets the DB2 database client to retrieve data in UTF‑8 format:
db2set DB2CODEPAGE=1208
When using the db2set command, add the location of db2set to the environment variable PATH. For example, if db2set is in $DB2DIR/adm and you use db2set in the pmd11.sh shell script, add the location of db2set to the environment variable PATH in pmd11.sh.
About the HP-UX11i Version 1 library path
The definition of the HP-UX11i in the environment variable SHLIB_PATH must put the path to ODBC and DB2 libraries before the AC_SERVER_HOME path. For example, if ODBC/lib and DB2DIR/lib are paths to the ODBC and DB2 libraries, use the following SHLIB_PATH definition:
SHLIB_PATH=$ODBC/lib:$DB2DIR/lib:$AC_SERVER_HOME/lib:usr/local/bin: