This section only refers to the ADABAS tools. For the call of precompilers and application programs, there are special precedence rules of passing the user specifications. These rules are described in the precompiler manuals.
When calling an ADABAS tool, the following order of precedence applies (highest priority first):
Connect data is passed with parameters when calling the tool,
Connect data is taken from the XUSER file,
SERVERDB is taken from the UNIX environment variable SERVERDB,
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 call of an ADABAS tool, these parameters are used to establish a database session. The user can directly access the operative mode of the tool. Example:
xquery -u parker,secret -d dbtest -n sql1
The same is true if the called tool uses additional user specifications such as TIMEOUT or ISOLATION LEVEL.
DEFAULT values possibly existing from an XUSER file or from UNIX environment variables are overridden.
2) If XUSER specifications are available, all missing and required user specifications are taken from the parameter combination 'DEFAULT'.
Examples:
xquery -u parker,secret
xquery -u parker -d dbprod -n sql1
xquery -u parker -d testdb
xquery -u parker
xquery -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'. The user can directly access the operative mode.
xquery
All user specifications are taken from the XUSER parameter combination 'DEFAULT'. The user can directly access the operative mode.
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 combination.
Examples:
xquery -U special -d dbprod
USERNAME, PASSWORD, and SERVERNODE are completed from the XUSER parameter combination 'special'.
xquery -U remsql
All user specifications are taken from the XUSER parameter combination 'remsql'. The user can directly access the operative mode.
4) If only the parameter SERVERDB is missing and no XUSER specifications exist, then the value of the environment variable SERVERDB is used to complete the user specifications.
5) If one of the required specifications cannot be found in any of these sources or if one of the specifications is incorrect, the called ADABAS tool returns the connect screen.