Was this helpful?
User-Definable Environment Variables and Logicals
Some Ingres environment variables and logicals 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 Ingres environment variables and logicals set system-wide.
UNIX: A good place to set user-defined environment variables is the user’s .login (for the C shell) or profile (for the Bourne Shell) file.
VMS: Individual users can define Ingres environment variables at the job or process level with DCL commands, or they can be defined in the user’s login.com 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
UNIX:
C Shell:
setenv TERM_INGRES vt100f
Bourne Shell:
TERM_INGRES=vt100f export TERM_INGRES
VMS:
DEFINE TERM_INGRES "VT100F"
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
UNIX:
BSD:
printenv
System V:
env
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.
Environment Variables and Logicals that Cannot Be Reset
The following Ingres environment variables and logicals 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
UNIX: These environment variables and logicals must not be visible using the env or printenv command.
Last modified date: 08/29/2024