(Contents)(Previous)

Precedence Rules of the Various Connect Procedures

This chapter only refers to the ADABAS tools. For the start of precompilers and application programs, there are special precedence rules of passing the user specifications. These rules are described in the precompiler manuals.

When starting an ADABAS tool, the following order of precedence applies (highest priority first):

Connect data is passed with parameters when starting the tool,

Connect data is taken from the SQL-DB.INI file,

i.e., each procedure of higher priority overrides the specifications of a less-priority procedure.

In detail, the following is true:

1) If the corresponding parameters for the required user specifications USERID, PASSWORD, SERVERDB, and SERVERNODE have been set for the start of an ADABAS tool, these parameters are used to establish a database session. You can directly access the operative mode of the tool. Example:

query -u parker,secret -d dbtest -n sql1

The same is true, if the started tool uses further user specifications such as TIMEOUT or ISOLATION LEVEL.

DEFAULT values possibly existing from the SQL-DB.INI file or from DOS environment variables are overridden.

2) If XUSER specifications are available, all missing and required user specifications are taken from the parameter combination 'DEFAULT'.

Examples:

query -u parker,secret

query -u parker -d dbprod -n sql1

query -u parker -d testdb

query -u parker

query -d testdb

In all cases, at least one of the required user specifications is missing:

- SERVERDB and SERVERNODE or

- PASSWORD or

- PASSWORD and SERVERNODE or

- PASSWORD, SERVERDB, and SERVERNODE or

- USERID, PASSWORD, and SERVERNODE

The missing specifications are taken from the XUSER parameter combination 'DEFAULT'. You can directly access the operative mode of the started tool.

query

All user specifications are taken from the XUSER parameter combination 'DEFAULT'. You can directly access the operative mode of the started tool.

3) If a special USERKEY was specified before the explicit specification of individual user parameters, the missing user specifications are completed from the corresponding XUSER parameter combinations.

Examples:

query -U special -d dbprod

USERNAME, PASSWORD, and SERVERNODE are completed from the XUSER parameter combination 'special'.

query -U remsql

All user specifications are taken from the XUSER parameter combination 'remsql'. You can directly access the operative mode of the started tool.

4) If one of the required specifications cannot be found in any of these sources or if one of the specifications is incorrect, the started ADABAS tool returns the connect window.


(Contents)(Previous)