Installation-Wide Environment Variables and Logicals

Ingres environment variables and logicals that are defined at the Ingres 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 in Windows and UNIX

Use Ingres Visual Manager to view Ingres environment variables and to manually register and deregister them. Additionally, you can use it to override certain environment variables at the user level.

To view environment variables in Ingres Visual Manager:

1. Select the Ingres Installation branch in Ingres Visual Manager.
2. Select the Parameters tab and select the System subtab (if not already selected).

   The Ingres parameters that are set at the installation (system) level are displayed.

3. Select the Show Unset Parameters check box.

   Parameters that are not currently set are displayed.

   If the User subtab is selected, those parameters that can be overridden at the user level are displayed.

4. Select the Extra subtab.

   Any extra Ingres environment variables that are added or variables whose names are dynamic are displayed. You can edit these parameters from this screen.

Alternatively, 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 Ingres symbol table, use the ingsetenv and ingunset utilities. Always use these commands to alter the symbol table. Never edit this file directly.

A similar set of system administrator commands are available to set, print, and unset installation-wide Ingres environment variables simultaneously for all clients of an Ingres installation server. These commands are ingsetall, ingprall, and ingunsetall.

View Environment Variables in VMS

Ingres logicals (with the exception of II_SYSTEM) are defined in II_CONFIG:config.dat during the install process. These logicals can be redefined locally using the operating system command define/job logical_name "value." However, to update the logical definitions permanently, the II_CONFIG:config.dat file must be manually edited and the logical definitions modified.

To facilitate user access to Ingres tools and logical definitions, add the following access commands to the users' login.com file when you log into the system.

For users, add:

@II_SYSTEM:[ingres]ingusrdef.com

For database administrators, add:

@II_SYSTEM:[ingres]ingdbadef.com

For the system administrator, add:

@II_SYSTEM:[ingres]ingsysdef.com

The commands in these files provide tools access to all users in a system-level installation and to all users with the appropriate group user identification code (UIC) in a group-level installation. The Ingres logicals contained in II_CONFIG:config.dat are redefined at a job level for each user when one of the above commands is executed.

You can display all installation-wide Ingres logicals by typing the following command at the operating system prompt:

show logical [/system|/group|/job] ii*

Example: Set the ING_EDIT Variable

ING_EDIT specifies the default editor invoked by various editor commands.

Windows and UNIX:

To set ING_EDIT for an installation using Ingres Visual Manager, follow these steps:

1. Log in as the system administrator
2. In the Ingres Visual Manager, select the Ingres Installation branch.
3. Select the Parameters tab, and select the System subtab.

   The Ingres parameters that are set at the installation (system) level are displayed.

   Note: For variables that have a dynamic name, select the Extra tab instead of the System tab.

4. Select the Show Unset Parameters check box to display parameters that are not currently set.
5. Choose ING_EDIT from the Parameters list, and double-click in the value area.
6. Edit the value and press Enter.
7. Alternatively, click Add and scroll to choose the ING_EDIT variable. Enter the required value, and click OK.

To set ING_EDIT using a system command, do the following:

1. Log in as the system administrator
2. At the operating system prompt type the following:

   Windows:

   ingsetenv ING_EDIT D:\TOOLS\VI.EXE

   UNIX:

   ingsetenv ING_EDIT /usr/bin/vi

   VMS:

   define [/table_level] logical_name "value"

Note: On VMS, the value assigned to the Ingres logical must be in double quotes.

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=IBMPC

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

Locally Resettable Environment Variables and Logicals

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.

Non-Locally Resettable Environment Variables and Logicals

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_COLLATION
• 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.