This appendix lists alphabetically the basic Ingres environment variables and logicals. Use this appendix as a reference for the chapter "Setting Environment Variables and Logicals."
Additional special purpose Ingres environment variables and logicals can be used in your installation, depending on the equipment and configuration.
|
|
DBNAME_ING specifies a startup file of set commands to be executed whenever a user opens the specified database (DBNAME) DBNAME_ING can be defined installation-wide or locally.
Windows: DBNAME_ING affects any user who connects to the database specified by DBNAME using the QUEL Terminal Monitor.
UNIX: DBNAME_ING is effective in all user interfaces, including a terminal monitor.
VMS: The syntax for defining this logical is:
define DBNAME_ING path_to_file
|
|
DBNAME_SQL_INIT specifies a startup file of set commands to be executed whenever a user connects to the database specified by DBNAME using the SQL single-line Terminal Monitor. It can be set installation-wide or locally. For details on using DBNAME_SQL_INIT, see the chapter "Setting Environment Variables and Logicals."
|
|
DD_RSERVERS points to the directory hierarchy that is used by the Replicator servers.
Note: DD_RSERVERS is not a required variable. If it is not set, it defaults to the "rep" subdirectory under the Ingres installation directory.
Windows: By default, DD_RSERVERS is defined to be %II_SYSTEM%\ingres\rep. To define a different location, use, for example:
set DD_RSERVERS c:\rep2
UNIX: By default, DD_RSERVERS is defined to be the $II_SYSTEM/ingres/rep. To define a different location, use, for example:
C Shell:
setenv DD_SERVERS /usr/rep2
Bourne Shell:
DD_RSERVERS=/usr/rep2; export DD_RSERVERS
VMS: By default, DD_RSERVERS is defined to be the II_SYSTEM:[ingres.rep]. To define a different location, use, for example:
define DD_RSERVERS user_disk:[rep2]
The $DD_RSERVERS/servers (DD_SERVERS:[servers] for VMS) directory contains server1 through server10. These directories are used by the Replicator servers during runtime.
If you need your installation to support multiple Replicator configurations and/or multiple source databases, use DD_RSERVERS to access each Replicator environment. For each environment, create a DD_RSERVERS directory with the subdirectory servers. In the servers directory, create subdirectories server1 through serverN where N is the number assigned to the Replicator Server.
|
|
II_4GL_DECIMAL determines the decimal point character for 4GL source input. For example, in France, the decimal point character is a comma. The default value is ".". Valid values are "." and ",".
|
|
II_AFD_TIMEOUT is used to set the number of seconds before timeout in Vision's Application Flow Diagram.
When you are using Vision's Application Flow Diagram, Vision periodically checks for changes made by concurrent developers that affect the diagram. If such a change has been made, Vision notifies you and gives you a chance to update the display.
You can set II_AFD_TIMEOUT to any value greater than 20, or 0 to disable the timeouts. Setting the value to much less than the default of 300 seconds causes Vision to time out and query the database often enough to visibly affect performance.
|
|
II_APPLICATION_LANGUAGE is set to the language Application-By-Forms uses to translate string constants.
ABF allows you to internationalize your applications by translating the string constants you define for them. When you run the application, it normally uses the constants defined for your default language. You can override this by defining II_APPLICATION_LANGUAGE to the name of another language. For more information, see Forms-based Application Development Tools User Guide.
|
|
II_BIND_SVC_xx is set to the bind address for Ingres tools connections to a named Ingres or Enterprise Access installation.
|
|
II_C_COMPILER is set to the value of the C compiler in use for ABF. Valid entries are VAX11(VAX/VMS only), DECC, or NONE. II_C_COMPILER is defined at the system or group level. (Call technical support for information about how to change the C compiler used by ABF).
|
|
II_CHARSETxx is used to set the type of character set used for string operations. This is set during installation and cannot be changed without corrupting data.
|
|
II_CHECKPOINT is an area set to the full file specification for the default checkpoint location. It is set during installation and cannot be changed, even during installation updates. Specific databases can designate alternate locations for checkpoints as a parameter to the createdb command.
|
|
II_CLIENT is set to "true" for client installations. Do not change II_CLIENT if it is set.
|
|
II_COLLATION determines the collating sequence for a database when the database is created. Valid entries are "multi" to specify the DEC Multinational Character Sequence or "spanish" to specify the Spanish alphabet's character sequence. More on collation sequences is described in Local Collation Sequences. II_COLLATION can be defined at the system level or redefined by the individual user at the process or job level.
|
|
II_CONFIG sets the full file specification of the Ingres files directory during the installation procedure. It cannot be changed.
|
|
II_CONNECT_RETRIES sets the number of times an application retries a connection before returning an error. The default is 1. An optional flag (d or D) causes a delay before the retry. For example: II_CONNECT_RETRIES=1d.
|
|
II_DATABASE is an area set to the full file specification for the default database location. It is set during installation and cannot be changed, even during installation updates. Specific databases can designate alternate locations as a parameter to the createdb command.
|
|
II_DATE_FORMAT defines the format style for date values. It is defined installation-wide. Default is the US value with an output format of dd-mmm-yyyy. Default legal input formats for US dates include:
mm/dd/yy
mm/dd/yyyy
dd-mmm-yyyy
mm-dd-yyyy
yyyy.mm.dd
yyyy_mm_dd
mmddyy
mm-dd
mm/dd
If set, it replaces the default format with an alternative format. The following are valid II_DATE_FORMAT settings, showing the alternative output format:
Setting |
Output Format |
|---|---|
US (default) |
dd-mm-yy |
ISO |
yymmdd |
MULTINATIONAL |
dd/mm/yy |
SWEDEN or FINLAND |
yyyy-mm-dd |
GERMAN |
dd.mm.yy |
DMY |
dd-mmm-yyyy |
MDY |
mmmm-dd-yyyy |
YMD |
yyyy-mmm-dd |
For example, if the logical's setting is ISO, the dates are output as yymmdd. If you enter a date using a similar, six-character format, such as mmddyy, the date is interpreted on output as yymmdd. For example, if you enter the date March 9, 1912, as 030912 (mmddyy) and II_DATE_FORMAT is set to ISO, this date is interpreted as Sept. 12, 1903 (030912 as yymmdd). You receive an error message if the date you entered cannot be interpreted as a valid date in the output format.
Note: When using the _date4() function (MULTINATIONAL4), the output format for the year value always returns 'yyyy'.
For more information about valid date input and output formats, see the SQL Reference Guide.
|
|
II_DATE_CENTURY_BOUNDARY determines the inferred century for a date that is missing the century on input. It can be set to an integer value in the range of 0 < n < =100. If this environment variable is not set in the user's environment or if it is set to 0 or 100, the current century is used.
The century is determined by the following calculation:
if ( date_year < II_DATE_CENTURY_BOUNDARY )
then
(date_year += 2000)
else
(date_year += 1900)
endif
For example, if II_DATE_CENTURY_BOUNDARY is 50 and the current year is 1999, an input date of 3/17/51 is treated as March 17, 1951, but a date of 03/17/49 is treated as March 17, 2049.
If the user enters the full four digits for the year into a four-digit year field in the application, the year is accepted as entered, regardless of the II_DATE_CENTURY_BOUNDARY environment variable setting.
|
|
II_DBMS_LOG points to the location of the log file containing DBMS server-specific error messages. It is set installation-wide. The server reads it at startup time, so changing it after startup has no effect on an existing server. Most error messages written to this file are also logged to the installation-wide error log (errlog.log). Some server trace messages and statistics information are written to the II_DBMS_LOG file that are not written to errlog.log. The default, if not set, is $II_SYSTEM/ingres/files/errlog.log.
|
|
II_DBMS_SERVER points to the DBMS Server to which the client process automatically connects. It can be set installation-wide or locally. When II_DBMS_SERVER is set, application processes bypass the Name Server. Using II_DBMS_SERVER requires setting II_GC_REMOTE in the DBMS Server installation.
|
|
II_DECIMAL specifies the character used to separate fractional and non-fractional parts of a number. Valid characters are the period (.) (as in 12.34) or the comma (,) (as in 12,34). The default is the period. This variable is set installation-wide.
Note: If II_DECIMAL is set to comma, be sure that when SQL syntax requires a comma (such as a list of table columns or SQL functions with several parameters), that the comma is followed by a space. For example:
select col1, ifnull(col2, 0), left(col4, 22) from t1:
|
|
II_DIRECT_IO is specific to UNIX environment. If set, it causes disk reads and writes to be done directly to disk, circumventing the UNIX file buffer system. It is only available on some platforms.
|
|
II_DISABLE_SYSCHECK controls the execution of the syscheck command. The syscheck command checks the system to confirm the availability of the required resources for running Ingres. If II_DISABLE_SYSCHECK is set, syscheck is still called but will immediately exit without performing any checks and with a success return status. For more information on the syscheck command, see Command Reference Guide.
|
|
II_DML_DEF defines the default query language for an installation as SQL or QUEL. It is used in installations that support both the SQL and QUEL database languages, in which case one such language can be designated as the default. Applications-By-Forms, Ingres 4GL, and Report-By-Forms are parts of the Ingres tools that use II_DML_DEF. SQL is the default if this is not set. It can be set installation-wide or locally.
|
|
II_DUMP defines an "area" that specifies the default location of the dump log files used in online backup. (For more information on online backup, see the ckpdb description in the Command Reference Guide.) It is defined installation-wide during installation and cannot be changed.
|
|
II_EMBED_SET allows application programs to set a variety of features. It can be set installation-wide or locally. The acceptable values and the actions they specify are:
Prints query that caused error.
Enables/disables saving of the text of the last query issued. Specify 1 to enable or 0 to disable. To obtain the text of the last query, you must issue the inquire_ingres(:query= querytext) statement. To determine whether saving is enabled, use the inquire_ingres(:status=savequery) statement.
Prints all query text and timing information to iiprtqry.log file in the current directory.
Specifies an alternate text file to which query information is written. The default file name is iiprtqry.log.
Traces GCA messages to the iiprtgca.log file in the current directory.
Specifies an alternate text file to which GCA information is written. The default file name is iiprtgca.log.
Enables or disables saving of DBMS trace messages to a text file (specified by tracefile). Specify 1 to enable saving of trace output, or 0 to disable saving.
Specifies an alternate text file to which tracepoint information is written. The default file name is iiprttrc.log.
Prints all errors and database procedure messages arising from embedded SQL statement.
Print events as they return from DBMS.
Makes local (DBMS) error numbers the default error numbers returned to the application in errorno and the SQLCA's sqlcode.
Makes generic error numbers the default error numbers returned to the application in errorno and the SQLCA's sqlcode.
Specifies the number of rows to be "prefetched" when retrieving data using cursors. Valid arguments are:
Ingres determines the number of rows to prefetch.
Disables prefetching. Each row is fetched individually.
Specifies the number of rows to be prefetched.
|
|
II_ERSEND is set during the installation procedure to the full path name of the errlog.log file.
|
|
II_FORCE_HET must be set to TRUE to allow seamless communication between the local client and remote databases on 64-bit HP Tru64 Alpha (formerly DEC Alpha) systems. II_FORCE_HET must be set before the client program attempts communication. For the change to take effect, the Communication Server and Name Server must be stopped and restarted.
|
|
II_FRS_KEYFIND allows users to turn off the keyfind frs function on table fields in read mode.
|
|
II_GC_REMOTE allows or disallows a direct connection between the application process on the client machine and the Ingres DBMS process on the server machine, thus bypassing Name Server processing. The vnode attribute, connection_type, must be set to "direct" to enable direct connections. For additional information on this vnode attribute, see the Connectivity Guide.
II_GC_REMOTE only needs to be set in the DBMS Server installation.
Valid II_GC_REMOTE values are:
On or Enable allows direct connections that use the vnode attribute as described above, and rejects direct connections that are attempted using the II_DBMS_SERVER environment variable.
Full or All allows both vnode controlled and II_DBMS_SERVER controlled direct connections. You must avoid using this setting because it compromises network security. (No validation occurs to determine whether the client installation has permission to access the server installation.)
If II_GC_REMOTE is not set, or is not set to one of the above values, direct connections are disallowed.
|
|
II_GCA_LOG denotes the output destination for II_GCx_TRACE trace information for all Ingres components. Can be set to stdio or to the full path to a file.
|
|
II_GCx_TRACE specifies environment variables and logicals for tracing:
Sets the trace level for General Communications Architecture (GCA)
Sets the trace level for Name Server (GCN)
Sets the trace level for Communication Server (GCC)
Sets the trace level for Data Access Server (GCD)
Sets the trace level for GCA Compatibility Library
Sets the trace level for GCC Compatibility Library
Each variable can be set separately to a number from 0 to 4 specifying trace level, with levels 1 through 4 increasing in amount of information traced.
If any of these values are set to non-zero, trace statements for the appropriate items are logged in the II_GCA_LOG file.
|
|
II_GCC_LOG denotes the output destination for the Communications Server (GCC) trace information. Setting this environment variable is preferable to using II_GCA_LOG because it is dedicated to the Communications Server process.
|
|
II_GCD_LOG denotes the output destination for the Data Access Server (GCD) trace information. Setting this environment variable is preferable to using II_GCA_LOG because it is dedicated to the Data Access Server process.
|
|
II_GCN_LOG denotes the output destination for the Name Server (GCN) trace information. Setting this environment variable is preferable to using II_GCA_LOG because it is dedicated to the Name Server process.
|
|
II_GCNxx_PORT contains the connect address of a local installation's Name Server. This variable must not be reset.
xx = 2-character code defined by II_INSTALLATION
|
|
II_HALF_DUPLEX, if set to 0 or undefined, enables Net duplex operation for SNA LU6.2 conversations. If set to 1, the Net half-duplex operation is enabled.
|
|
II_HELP_EDIT, if set to any value, adds an extra operation, Edit, to menus encountered in help text screens in the forms systems. The Edit operation enables users to edit the help text in the screen with the text editor defined by ING_EDIT. II_HELP_EDIT is typically defined locally by the individual user.
|
|
II_INSTALLATION is a two-character code used to define a specific instance of Ingres. It is also referred to as an instance ID. This code is set during installation. To change it, rerun the installation program.
|
|
II_JOURNAL is set to the full file specification for the default journal location. It is set during installation and cannot be changed, even during installation updates. Specific databases can designate alternate locations for journals as a parameter to the createdb command.
|
|
II_LANGUAGE determines what language is used for screen messages, menu items, and prompts. It is defined installation-wide. Valid values are as follows:
ENGLISH English (Default)
DEU German
ESN Spanish
FRA French
ITA Italian
JPN Japanese
PTB Brazilian Portuguese
SCH Simplified Chinese
|
|
II_LOG_DEVICE specifies the name of the logging/locking pseudo device to which the logging/locking driver is connected. This value is QAA0: for production installations. For test installations, the value is QxA0:, where x is the first character of the group installation identifier. This logical is defined at the system or group level.
|
|
II_MONEY_FORMAT defines the format of money output. It is set installation-wide. You can change the format by setting II_MONEY_FORMAT to a string with two symbols separated by a colon (:). The symbol to the left of the colon indicates the location of the currency symbol. It must be "L" for a leading currency symbol or a "T" for a trailing currency symbol. The symbol to the right of the colon is the currency symbol you want displayed. Currency symbols can contain up to 4 physical characters. For example:
Logical Definition Result
L:$ $100
T:DM 100DM
T:F 100F
|
|
II_MONEY_PREC specifies the number of decimal places to be displayed for money values. Valid values are 0, 1, and 2. The default is 2 (for decimal currency). It is set installation-wide. II_MONEY_PREC is applied when a money value is converted to a character string (for printing, for example). Extra decimal places are rounded. For example, if II_MONEY_PREC is set to 0, 9.50 is rounded to 10.
|
|
II_MSGDIR sets the directory containing error and information messages. Users must not change this setting. The default file is the II_LANGUAGE setting, located at $II_SYSTEM/ingres/files/english.
|
|
II_NULL_STRING specifies the string used by a terminal monitor and other Ingres tools to represent the null value. The string consists of one to three characters. The default value is three blanks.
|
|
II_NUMERIC_LITERAL, if set to FLOAT, tells Ingres to interpret the data type of floating-point constants or result variables to be float8 rather than decimal, which is the default. For more information, see Decimal Constant Semantics Change in the Migration Guide.
Note: II_NUMERIC_LITERAL should be used only temporarily for easing migration from Ingres 6.4.
|
|
II_NUM_OF_PROCESSORS is set to the number of processors on the machine. The variable affects processing in the Ingres DBMS, particularly when waiting for mutually exclusive resources; a value larger than 1 causes a more compute-intensive strategy that may result in getting the resource faster; however, this strategy is not generally advisable on single processor machines.
|
|
II_NUM_SLAVES specifies the number of slave processes that a DBMS server creates to do disk operations. The default is two, but systems having applications with high I/O throughput requirements, many disks, or faster disk drives can increase the number of slave processes. The following example allows each new server that is started to have four slaves:
ingsetenv II_NUM_SLAVES 4
Stop and restart DBMS servers to reset the number of slaves. The maximum supported value is 30 and the minimum is 0. Setting this environment variable/logical to 0 degrades performance substantially.
Note: On UNIX implementations that use O/S threads, II_NUM_SLAVES is not set and there are no I/O slaves.
|
|
II_OO_TABLE_SIZE allows you to increase the size of an internal COPYAPP table to support the copying of more application objects than is allowed by the default (4096 objects).
|
|
II_PATTERN_MATCH determines the set of pattern matching characters for QBF and the ABF qualification function. These can be SQL-like, QUEL-like, or not set.
The pattern matching characters used by QBF and the ABF qualification function are % _ [ and ]. The % is equivalent to the QUEL"*" and _ is equivalent to the QUEL "?".
The pattern matching characters used by QBF and the ABF qualification function are * ? [ and ].
If not set, or if it is set to anything other than sql or quel, the QUEL pattern matching characters are used.
II_PATTERN_MATCH can be set installation-wide or locally. The complete word, either sql or quel, must be entered. The setting for II_PATTERN_MATCH is case-sensitive.
|
|
II_PF_NODE specifies the vnode name of a remote node to be managed through the Microsoft Windows Performance Monitor.
|
|
II_POST_4GLGEN specifies a command to be translated and executed by the Vision component following successful generation of Ingres 4GL code. The command is passed the full path name of the Ingres 4GL source file just generated. This logical is used only by sites that have installed the Vision product. For more information on this logical, see the Forms-based Application Development Tools User Guide.
|
|
II_PRINTSCREEN_FILE is used with the printscreen function. It specifies a default file name for the output file of the printscreen function. This environment variable/logical is usually defined locally by the individual user. If this environment variable/logical is set and no file name is sent to the printscreen function, no prompt is given and this file name is used. If not set, the user is prompted for a file name. If the file name "printer" is specified for II_PRINTSCREEN_FILE, the screen depiction is sent directly to the line printer. For more information, see the Character-based Querying and Reporting Tools User Guide.
|
|
II_SQL_INIT can be set locally to the full path name of a file containing SQL commands. Typically, it is defined locally by the individual user. When a user with II_SQL_INIT set connects to a terminal monitor, the commands in the named file are processed.
|
|
II_STAR_LOG points to the location of the log file containing distributed DBMS server-specific error messages. It is set installation-wide. It is read by the server at startup time, so changing it after startup has no effect on an existing server. Most error messages written to this file are also logged to the installation-wide error log (errlog.log). Some server trace messages and statistics information are written to the II_STAR_LOG file that are not written to errlog.log. The default, if not set, is $II_SYSTEM/ingres/files/errlog.log.
|
|
II_SYSTEM specifies an "area" that specifies the parent directory of the ingres directory, where many components of your installation are located. It must not be changed without reinstalling Ingres.
|
|
II_TEMPORARY specifies the directory where temporary files used by the Ingres tools are created. By default, these files are created in the user's current directory. II_TEMPORARY can be redefined installation-wide or locally.
|
|
II_TERMCAP_FILE specifies an alternative termcap file to use. This file must be in Ingres termcap file format. It can be redefined installation-wide or locally.
|
|
II_TFDIR specifies the directory in which the Vision code generator searches for Ingres 4GL template files. This logical is used only by sites that have the Vision component installed.
|
|
II_THREAD_TYPE specifies whether Ingres uses internal threads or OS threads. Valid settings are:
Operating System threads
Internal threads
This variable can be set during installation. For additional information on setting this variable for your platform, see the Readme file.
|
|
II_TIMEZONE_NAME specifies the world time zone that determines the installation's location for timing purposes. It is defined during installation.
|
|
II_TM_ON_ERROR defines the action taken when an error occurs in a terminal monitor. The valid settings are continue (on error) or terminate (on error). If this environment variable/logical is not set, the default action for the (non-forms based) terminal monitor is to continue; the default for Interactive SQL or QUEL (the forms-based terminal monitor) is to terminate. It can be defined installation-wide or locally by the individual user.
|
|
II_TUXEDO_LOC supports Ingres DTP for Tuxedo. Specifies the directory where the shared memory file is to be created. It must be the same for all servers in a group. If II_TUXEDO_LOC is not set, II_TEMPORARY is used.
|
|
If II_TUX_SHARED is set to USER, the name of the shared memory segment used by Ingres is t<username>.tux; otherwise the name is t1.tux.
|
|
II_TUX_AS_MAX is the maximum number of application and TMS servers that can be started. The default value is 32. A maximum of II_TUX_AS_MAX servers are permitted to attach to the Ingres shared memory segment.
|
|
II_TUX_XN_MAX is the total number of transaction entries allocated in the shared memory segment. Each server that attaches the shared memory segment reserves II_XA_SESSION_CACHE_LIMIT transaction entries for its own use. The default value is 1024.
|
|
II_UNICODE_CONVERTER sets the converter to be used for Unicode coercion. The DBMS Server carries out the coercion of Unicode data to local character set value based on the Unicode converter (or mapping table). Several converters are available in compiled and xml format, located in the directory $II_SYSTEM/ingres/files/ucharmaps. By default, Ingres automatically chooses the converter to use, based on the encoding used by the locale on your system.
You can manually set II_UNICODE_CONVERTER if Ingres is unable to set the converter correctly for your locale for coercing Unicode data to local character set value.
To manually set II_UNICODE_CONVERTER on UNIX based on locale
locale
The locale on your system is returned.
LC_CTYPE=ja_JP.sjis locale charmap
The character set used by the system is returned.
ingsetenv II_UNICODE_CONVERTER mapping_id
Recycle the server by issuing the ingstop and the ingstart commands.
|
|
II_UUID_MAC, when set to TRUE, uses an older algorithm for generating UUIDs on Windows.
For security reasons, the uuid_create function on Windows no longer uses a machine's MAC address to generate UUIDs. You can use the II_UUID_MAC environment variable if you do not need the level of security provided by the new uuid_create algorithm and for the sake of compatibility want to continue to use the MAC address of your machine when creating UUIDs.
|
|
II_VNODE_PATH specifies a series of remote virtual nodes to be tried each time a user attempts to connect to the specified vnode. Node names are specified as strings to be appended to vnode. Commas must separate the strings.
For example, the following specifies that the remote virtual nodes mynode0, mynode1, mynode2, and mynode3 be tried each time a user attempts to connect to mynode:
II_MYNODE_PATH=0, 1, 2, 3
The names must be valid remote virtual nodes defined by the Ingres Network Utility or the Net Management Utility (netutil).
A single connection attempt begins with one of the nodes, chosen at random, and continues until all of the specified nodes have been tried. The number of connection attempts made before an error is returned to the user is determined by the value of II_CONNECT_RETRIES.
|
|
II_WORK specifies a directory that contains temporary files used by Ingres during the execution of certain queries such as sorts, copies, and modifies.
|
|
II_XA_TRACE_FILE specifies a file in which Ingres DTP (Distributed Transaction Processing) logs the events occurring through the TMXA interface, as well as any SQL performed against the Ingres DBMS. The user who starts the application servers must have write access to the file. For additional information about this file, see the Distributed Transaction Processing User Guide.
|
|
IIDLDIR specifies a directory that contains dynamically loaded libraries.
|
|
ING_ABFDIR defines the directory name for the top-level directory to contain Application-By-Forms object libraries and work files. Under this directory, a subdirectory is created for each database that contains ABF applications and, within that subdirectory, another subdirectory is created for each ABF application. The ING_ABFDIR directory level must have read, write, and execute permissions for group, owner, and world. If, however, the application designer redefines ING_ABFDIR to point to a directory of his own, he can optionally restrict permissions on the directory to read, write, execute to owner. It can be redefined installation-wide or locally.
|
|
ING_ABFOPT1 specifies the name of a file, used by ABF, in which additional linker options can be placed. These options are not required to run ABF applications but can be required to include libraries, compiled objects, and other capabilities not available in ABF. Users can modify this file. For more information, see the Forms-based Application Development Tools User Guide. The individual user usually defines it at the local level.
|
|
ING_EDIT specifies the default editor invoked by various editor commands. The default for the entire installation is set during the installation procedure. Users can also set this in their local environment.
Windows: You must set ING_EDIT to the full path name of the editor. For example:
c:\tools\vi.exe
UNIX:
/usr/ucb/vi
VMS: If undefined, the callable EDT editor is called. ING_EDIT can be defined to be:
Calls the EDT editor.
Calls the TPU editor.
Calls the language sensitive editor.
The "+" symbol indicates that the callable version of the editor is to be used. This avoids creating a new subprocess in which to run the editor and results in much faster start up of the editor when called from a terminal monitor, ABF and other Ingres tools programs. Example:
DEFINE ING_EDIT "+TPU"
No qualifiers can be used. You must specify any non-default editor behavior in an editor startup file. For example, to use the Language Sensitive Editor in FORTRAN, define the following:
DEFINE ING_EDIT "+LSE" DEFINE LSE$COMMAND - "SYS$LOGIN:LSE_STARTUP.LSE"
|
|
ING_PRINT specifies the default printer command issued by the Print function. The default is PRINT. It is usually defined locally by the individual user.
|
|
ING_SET specifies a quoted string or startup file of set commands to be executed whenever a user connects to the DBMS Server through an application, an Ingres tool, or a single-line terminal monitor. It can be set installation-wide or locally. For details on using ING_SET, see the chapter "Setting Environment Variables and Logicals."
|
|
ING_SET_DBNAME specifies a quoted string or startup file of set commands to be executed whenever a user connects to the database specified by DBNAME. Affects any user who connects to the specified database through an application, an Ingres tool, or a single-line terminal monitor. It can be set installation-wide or locally. For details on using ING_SET_DBNAME, see the chapter "Setting Environment Variables and Logicals."
|
|
ING_SHELL, If defined, contains the path name of the shell used by Ingres Menu and a terminal monitor when the shell operation is invoked.
|
|
ING_SYSTEM_SET specifies a quoted string or startup file of set commands to be executed whenever a user connects to the DBMS Server through an application, an Ingres tool, or a terminal monitor. It is always global. For details on using ING_SYSTEM_SET, see the chapter "Setting Environment Variables and Logicals."
|
|
INGRES_KEYS specifies a mapping file to customize a user's keyboard layout for use with forms based programs. For a complete description of the mapping file syntax, see Character-based Querying and Reporting Tools User Guide. This environment variable/logical is usually set in the user's local environment.
|
|
INIT_INGRES can be set to the full file specification of a file containing QUEL commands. It is usually defined locally by the individual user. When a user with INIT_INGRES set connects to the QUEL Terminal Monitor, the commands in the named file are processed. For details on using INIT_INGRES, see the chapter "Setting Environment Variables and Logicals."
|
|
TERM is the terminal description for the terminal upon which you are executing UNIX programs. The TERM environment variable is not used directly, but it becomes the default for TERM_INGRES, if TERM_INGRES is not explicitly set. TERM is used by UNIX programs like vi, which can be called as subsystems from Ingres programs.
|
|
TERM_INGRES contains the terminal designation for the terminal upon which you are executing one of the Ingres forms-based products, such as QBF or VIFRED. For a list of supported values, see Character-based Querying and Reporting Tools User Guide. It is usually defined locally by the individual user.
Windows: TERM_INGRES is most conveniently set in the symbol table to IBMPC.
UNIX: TERM_INGRES is most conveniently set in a .login or .profile file. TERM_INGRES takes precedence over TERM in defining the terminal type. It allows TERM to be defined differently for use by other UNIX programs such as vi.
VMS: TERM_INGRES is most conveniently set in a LOGIN.COM file.