User specifications for the precompiler call are only required when the option CHECK (default) or SYNTAX is set. If the application runs in multi-db mode, user specifications are needed for each of the up to eight database sessions. If the precompiler option NOCHECK is set, a database session is not opened, so that no user specifications are necessary. The concept of how a user can connect to a database, the possible user specifications, and the syntax according to which the user specifications have to be made are described in the platform-specific ADABAS User Manuals.
The following precedence rules are applied to the user specifications (USER, PASSWORD, SERVERNODE, SERVERDB, TIMEOUT, CACHELIMIT, SQLMODE and isolation level):
1. If the statically first SQL statement of a database session is not a CONNECT statement, then all the user specifications are fetched from the XUSER file.
2. If the statically first SQL statement of a database session is a CONNECT statement, then all the specifications made in this statement are taken and the missing specifications are fetched from the XUSER file.
3. For the database session with the number 1, the user specifications can be overridden by means of the corresponding precompiler options.
The precompiler option isolation-level is passed to the application program. It overrides the specifications made in the application program. Isolation level can be overridden by means of runtime options.