Was this helpful?
Installation-Wide Environment Variables
Vector environment variables that are defined at the Vector system or installation-wide level affect all users in an installation. These are usually defined during the install procedure. However, the system administrator can reset some manually.
View Environment Variables
To view all installation-wide environment variables from the command line, enter the following command at the operating system prompt:
ingprenv
To manually register or to remove an environment variable from the symbol table, use the ingsetenv and ingunset commands. Never edit the symbol table file directly.
For example, to change the value of II_DECIMAL (character used to separate fractional and non-fractional parts of a number) from a period to a comma, issue this command:
ingsetenv II_DECIMAL ,
A similar set of system administrator commands are available to set, print, and unset installation-wide Vector environment variables simultaneously for all clients of a server installation. These commands are ingsetall, ingprall, and ingunsetall.
User-definable Environment Variables
Some Vector environment variables can be set or reset by individual users in their local environment using operating system commands. Those set in a user’s local environment supersede the Vector environment variables set system-wide.
Linux: A good place to set user-defined environment variables is the user’s .bashrc or profile file.
To set an environment variable in the local environment
Use the command appropriate to your environment.
For example, an environment variable typically set in the user’s local environment is TERM_INGRES. It specifies the termcap definition to be used by the forms system. It can be redefined locally by entering commands at the operating system prompt:
Linux:
export TERM_INGRES=konsolel
Windows:
SET TERM_INGRES=IBMPC
To display the values set in your user environment
Enter the following command at the operating system prompt:
Windows:
SET
Linux:
printenv
Environment Variables that Can be Reset Locally
In general, only the following Vector environment variables must be set in your local environment:
Windows:
II_SYSTEM
PATH
Linux:
II_SYSTEM
PATH
The following Vector environment variables can be reset by users in their local operating system shell:
DBNAME_SQL_INIT
II_DATE_FORMAT
II_DBMS_SERVER
II_DECIMAL
II_EMBED_SET
II_GC_REMOTE
II_GCA_LOG
II_GCx_TRACE
II_LANGUAGE
II_MONEY_FORMAT
II_MONEY_PREC
II_NULL_STRING
II_PRINTSCREEN_FILE
II_SQL_INIT
II_SYSTEM
II_TEMPORARY
II_TERMCAP_FILE
II_TIMEZONE_NAME
II_TM_EXIT_ON_ERROR
II_TM_ON_ERROR
II_VNODE_PATH
II_WORK
IIDLDIR
ING_EDIT
ING_PRINT
ING_SET
ING_SET_DBNAME
ING_SHELL
INGRES_KEYS
INIT_INGRES
TERM
TERM_INGRES
IMPORTANT!  II_TIMEZONE_NAME can be reset for client installations only. Server installations must not reset this variable because it may affect date conversions from the local system time to the internal GMT-based value.
Environment Variables that Cannot Be Reset
The following Vector environment variables must not be reset by users:
II_BIND_SVC_xx
II_C_COMPILER
II_CHARSETxx
II_CHECKPOINT
II_CLIENT
II_CONFIG
II_CONNECT_RETRIES
II_DATABASE
II_DBMS_LOG
II_DIRECT_IO
II_DUMP
II_ERSEND
II_GCNxx_PORT
II_INSTALLATION
II_JOURNAL
II_LOG_DEVICE
II_MSGDIR
II_NUM_SLAVES
II_TUXEDO_LOC
II_TUX_SHARED
II_TUX_AS_MAX
II_TUX_XN_MAX
II_XA_TRACE_FILE
ING_SYSTEM_SET
Linux: These environment variables must not be visible using the env or printenv command.
Last modified date: 11/09/2022