Every ADABAS application program operates under a particular ADABAS user identification. Coupling the program to a user identification guarantees data security, because the program can only execute actions valid for this user identification. If a user identification is not specified explicitly (CREATE USER ... NOT EXCLUSIVE), ADABAS gives every user identification exclusively to one user. The user identification is not bound to a person, but is an authorization profile.
Furthermore, users can be united to form a group. Then every user has the privileges that have been determined for the group.
Before a user can work with a database, he has to open a database session. This means that he has to connect to a database. This is usually done via the CONNECT statement, but can also be done by means of predefined user specifications (XUSER; see the ADABAS user manuals).
If a CONNECT statement is specified in the program, the user identification and password can either be included in the text of the program or specified via host variables. The lock mode for the database session has to be specified in addition (for more information, see Section Locks).
COMMIT WORK RELEASE or ROLLBACK WORK RELEASE must be executed as the dynamically last SQL statement of an application program. COMMIT WORK RELEASE concludes the last transaction, ROLLBACK WORK RELEASE resets the effects of the last transaction. The additional specification RELEASE makes the ADABAS task which was serving the program available again to other database users.
Example:
