This chapter describes the most commonly used Ingres environment variables and logicals and the system level at which they are typically set.
|
|
|
Ingres has a set of available logical names through which you can define various file names and other values. For an alphabetical list of the basic Ingres environment variables and logicals, see the appendix "Environment Variables and Logicals."
Ingres uses the following types of operating-system dependent environment variables and logicals:
Windows:
UNIX:
Ingres environment variables in UNIX and Windows are active only when you are using Ingres. A small subset of these environment variables can be reset by the user in the local environment.
VMS:
Ingres logicals are defined in the appropriate logical name table.
|
|
|
Most Ingres environment variables in Windows and UNIX are set in the Ingres symbol table (symbol.tbl) and are visible only with the user command ingprenv.
When setting, unsetting, or changing environment variables, a backup of the symbol.tbl file, called symbol.bak, is maintained. If the original symbol.tbl file becomes corrupted, you can use the backup symbol table file to restore it.
A history of updates to the symbol.tbl file is maintained in the symbol.log file. The symbol.log file contains information on the types of updates performed as well as some application information.
The symbol.bak and symbol.log files are located in the II_CONFIG location or the II_ADMIN location (in the case of NFS Ingres instances).
|
|
|
Windows environment variables are set at the operating system level. These take effect before, during, and after Ingres is invoked. II_SYSTEM and PATH are the only environment variables used directly by Ingres. These are set in the user's environment using the following commands entered at the operating system prompt:
set environment_variable=value
The Windows environment variables are set using Ingres Visual Manager (IVM). For more information, see the IVM online help topic, Parameters Page, Ingres Installation branch.
Alternatively, you can set Windows environment variables through the Control Panel.
|
|
|
UNIX environment variables are set at the UNIX operating system level. These are in effect before, during, and after Ingres is invoked. II_SYSTEM, PATH, and TERM are the only UNIX environment variables required and used directly by Ingres. These environment variables are set in each user's environment using the following UNIX commands entered at the operating system prompt:
C Shell:
setenv environment_variable value
Bourne Shell:
environment_variable= value; export environment_variable
The environmental variables are typically set in a user's .login or .profile file, but can also be set in operating system startup scripts such as /etc/login.
|
|
|
VMS logicals are set in the system or group logical table and are visible with the system command, show logical/system or show logical/group. These are in effect before, during, and after Ingres is invoked. II_SYSTEM is the only VMS logical required and used directly by Ingres. This logical is defined by the system administrator using the following VMS command entered at the operating system prompt:
define [/table_level] logical_name "value"
The value assigned to the Ingres logical must be enclosed in double quotes.
This definition is typically placed in the operation-system wide command procedure for defining site-specific logical names (sys$manager:sylogicals.com).