Starting XUSER
XUSER is started by double-clicking the icon 
.
XUSER distinguishes between the first and subsequent start commands. It is not possible to specify options for the first start. For the first group of parameters, the input window is displayed at once. For all the other starts, it is necessary to connect with USERID and PASSWORD from the first parameter combination that contains a non-empty USERID.
The connect can be done with the option -u in the start command or from the connect window of XUSER.
Structure of the XUSER Window
Up to 32 parameter combinations can be saved. Each consists of
USERKEY: Key name used to access the combination.
The first parameter combination is named 'DEFAULT'.
This name cannot be modified.
USERID: ADABAS user name.
PASSWORD: ADABAS password of the user.
SERVERDB: Name of the ADABAS database to be used.
SERVERNODE: Name of the network node where the addressed database resides.
SQLMODE: ensures the compatibility with the SQL dialects of other manufacturers. Possible specifications are ADABAS, ANSI, or ORACLE. Default is ADABAS. This parameter is effective for precompiler programs and the tools LOAD and QUERY.
CACHELIMIT: Limit for the size of a temporary data buffer (only affects application programs with large SELECT results).
TIMEOUT: Time interval in seconds at the end of which an inactive session of the user is terminated: see ADABAS Reference Manual, Chapter Transactions, <connect statement>.
ISOLATION: ISOLATION LEVEL for locks that affect the user (only valid for application programs, precompilers): see ADABAS Reference Manual, Chapter Transactions, <connect statement>.
The password is invisible and must be entered twice for security reasons.
USERKEY, SERVERDB, and SERVERNODE are case sensitive.
USERNAME and PASSWORD must be enclosed in double quotation marks, as in database operation if they are to contain lowercase letters or special characters. Otherwise, lowercase characters are converted into uppercase.
The SQLMODE can be specified in any notation. If not specified, the default value ADABAS is valid.
CACHELIMIT, TIMEOUT, and ISOLATION are numeric parameters. If the respective default value is to be used for these parameters, -1 must be specified as value. In the empty input window, the default values are already set for these parameters.
The current number of the group of parameters is displayed in the header line of the input window. One group is displayed per page.
The following functions can be executed by using the keys displayed in the menu:
Save: Saving the current parameter combinations and subsequently leaving XUSER.
uit: Leaving XUSER without saving.
elete: Deleting an individual combination. Subsequent parameter combinations move upward.
Note: The parameter combination moved to the first place is automatically assigned the USERKEY 'DEFAULT'. The deletion only becomes effective if XUSER is left with SAVE.
revious: Scrolling to the previous parameter combination.
ext: Scrolling to the next parameter combination.
bout: Informing about copyright and version.
Saving the User Specifications in a Separate File
In some cases, it may be desired that the user specifications are not saved in the SQL-DB.INI file but in a separate file (e.g., on a floppy disk) and are read from there on starting the tool. This can be required for security reasons to prevent unauthorized PC users from accessing the database, but nevertheless ensuring authorized users a convenient connect to the database.
In this case, the following entry must be made to the SQL-DB.INI file (which is located in the Windows directory) by using a text editor.
If there is already a section [User] in the SQL-DB.INI file, the line
File=<filename>
must be entered as the first line. If the section [User] should not yet exist, it must be created first.
Example:
...
[User]
File=A:\USER.FIL
...
Subsequently, the file 'A:\USER.FIL' is used instead of the SQL-DB.INI file for saving and reading the user specifications.
Note: If the user specifications already saved in the SQL-DB.INI file are to be used further, the former section [User] can be saved into the new file to be created. The contents of this file could then run as follows:
[User]
User1=DEFAULT,SQLTRAVEL00,58a91f58 89336d4f cc0d9bb1 3f446464 3ae0f5f0 c820587b
Node1=sqlserv,DB61
Connect1=,-1,-1,-1
User2=demo,DEMO,d3351f1f 381aacdc c664abef 591acc60 d4259227 2ad9fe60
Node2=sqlserv,DB61
Connect2=,-1,-1,-1