4. Setting Environment Variables and Logicals : Installation-Wide Environment Variables : User-Definable Environment Variables and Logicals : Environment Variables and Logicals that Can Be Reset Locally
 
Share this page                  
Environment Variables and Logicals that Can Be Reset Locally
In general, only the following Ingres environment variables and logicals must be set in your local environment:
Windows:
II_SYSTEM
PATH
UNIX:
II_SYSTEM
PATH
VMS:
II_SYSTEM
The following Ingres environment variables and logicals 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.