System Administrator Guide > System Administrator Guide > Setting Environment Variables > Installation-Wide Environment Variables > User-Definable Environment Variables
Was this helpful?
User-Definable Environment Variables
Some Actian X 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 Actian X environment variables set system-wide.
Linux: A good place to set user-defined environment variables is the user’s profile file.
Example: Set an Environment Variable in the Local Environment
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 as in the following example:
Windows:
SET TERM_INGRES=IBMPCD
Linux:
TERM_INGRES=vt100f export TERM_INGRES
Display Current Value for Variables
A user can display the values set in their environment with the following command entered at the operating system prompt:
Windows:
SET
Linux:
env
Environment Variables that Can Be Reset Locally
In general, only the following Actian X environment variables must be set in your local environment:
Windows:
• II_SYSTEM
• PATH
Linux:
• II_SYSTEM
• PATH
The following Actian X environment variables can be reset by users in their local operating system shell:
• DBNAME_ING
• DBNAME_SQL_INIT
• II_4GL_DECIMAL
• II_ABF_RUNOPT
• II_AFD_TIMEOUT
• II_APPLICATION_LANGUAGE
• II_DATE_CENTURY_BOUNDARY
• II_DATE_FORMAT
• II_DBMS_SERVER
• II_DECIMAL
• II_DML_DEF
• II_EMBED_SET
• II_FRS_KEYFIND
• II_GC_REMOTE
• II_GCA_LOG
• II_GCx_TRACE
• II_HELP_EDIT
• II_LANGUAGE
• II_MONEY_FORMAT
• II_MONEY_PREC
• II_NULL_STRING
• II_PATTERN_MATCH
• II_PF_NODE
• II_POST_4GLGEN
• II_PRINTSCREEN_FILE
• II_SQL_INIT
• II_SYSTEM
• II_TEMPORARY
• II_TERMCAP_FILE
• II_TFDIR
• II_TIMEZONE_NAME
• II_TM_ON_ERROR
• II_VNODE_PATH
• II_WORK
• IIDLDIR
• ING_ABFDIR
• ING_ABFOPT1
• 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 logical 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 Actian X 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 command.
Last modified date: 08/14/2024