The CL command ends an ET session and updates the database.
We recommend that you set unused ACB and ACBX fields to binary zeros before the direct call is initiated.
This document covers the following topics:
The CL command is used to terminate a user session. Software AG recommends that all user programs issue a CL command upon completion of database processing. User programs operating in single-user mode which are performing database updating must issue a CL command to ensure that all updates have been written to the database.
A CL command:
issues an implicit ET command (ET-logic users only);
stores user data in an Adabas system file (optional);
releases all records currently in hold status for the user as well as all command ID entries (and corresponding ISN lists) assigned to the user;
transfers the user's ET data from the Adabas Work to an Adabas system file. This is done only if a user ID was provided with the OP command; otherwise, any ET data stored during the session is lost.
A CL command issued by a user operating in single-user mode causes a physical close of the database (Associator, Data Storage, Work, and the data protection log). It is therefore not possible for a single-user mode user to follow a CL command with another command (for example, an OP command).
This section describes ACB interface direct calls for the CL command. It covers the following topics:
| Field | Position | Format | Before Adabas Call | After Adabas Call |
|---|---|---|---|---|
| 1-2 | -- | -- | -- | |
| Command Code | 3-4 | alphanumeric | F | U |
| Command ID | 5-8 | binary | -- | A |
| File Number *** | 9-10 | binary | F | U |
| Response Code | 11-12 | binary | -- | A |
| ISN | 13-16 | binary | -- | A |
| ISN Lower Limit | 17-20 | binary | -- | A |
| ISN Quantity | 21-24 | binary | -- | A |
| 25-26 | -- | -- | -- | |
| Record Buffer Length | 27-28 | binary | F * | U |
| 29-35 | -- | -- | -- | |
| Command Option 2 | 36 | alphanumeric | F | U |
| 37-72 | -- | -- | -- | |
| Command Time | 73-76 | binary | -- | A |
| User Area | 77-80 | -- | -- | U |
| Buffer | Before Adabas Call | After Adabas Call |
|---|---|---|
| Format * | ** | -- |
| Record * | F | U |
where:
| F | Supplied by user before Adabas call |
| A | Supplied by Adabas |
| U | Unchanged after Adabas call |
| * | Required only if user data is to be stored |
| ** | Not used but must be included in parameter list of call statement if user data to be stored |
| *** | A database ID is only necessary if you are accessing a database other than the application's default database (read in by ADARUN DBID parameter, provided in the loaded link globals table, or linked with the link routine). |
| -- | Not used |
We recommend that you set unused ACB fields to binary zeros before the direct call is initiated.
CL
For ET logic users, Adabas returns the transaction sequence number of the user's last successfully executed transaction in this field. The number is provided in binary format.
Because the CL command includes an ET command (see Function and Use), it also increments the transaction sequence number by one (regardless of whether it completes a transaction with or without update commands). The incremented transaction sequence number is then returned.
The CL command returns binary zeros if it ends the session of an ET user without update commands.
A database ID is only necessary if you are accessing a database other than the application's default database (read in by ADARUN DBID parameter, provided in the loaded link globals table, or linked with the link routine).
In this field, Adabas returns the response code for the command. Response Code 0 indicates that the command was executed successfully. If the CL command returns a nonzero response code, the rightmost two bytes of the Adabas control block, Additions 2 field (bytes 47 and 48) may contain a subcode defining the exact response code meaning. Response codes and their subcodes are defined in the Adabas Messages and Codes Manual documentation.
Adabas returns the number of I/O operations resulting from this session's Adabas calls in this field.
In this field, Adabas returns the number of commands issued by the user during the user session.
In this field, Adabas returns an estimate of the amount of processor time used by this user for Adabas command processing.
The time is provided in units of 1.048576 seconds.
If user data is to be stored in an Adabas system file, the length of the record buffer must be specified in this field. The length specified determines the number of bytes of user data to be stored.
The maximum length which may be specified is 2000 bytes.
If no user data is to be stored, this field is not used.
| Option | Description |
|---|---|
| E | Indicates that user data is to be stored in an Adabas system file. |
The user program has completed all database activity and issues the CL command. No user data is to be stored.
| Command Code | CL | |
|---|---|---|
| Command Option 2 | b | no user data is to be stored |
The user program issues a CL command and provides user data to be stored in an Adabas system file.
| Command Code | CL | |
|---|---|---|
| Record Buffer Length | 17 | 17 bytes of user data to be stored |
| Command Option 2 | E | user data is to be stored |
| Record Buffer | USER 7 NORMAL END |
|---|
This section describes ACBX interface direct calls for the CL command. It covers the following topics:
| Field | Position | Format | Before Adabas Call | After Adabas Call |
|---|---|---|---|---|
| 1-2 | --- | --- | --- | |
| Version Indicator | 3-4 | binary | F | U |
| 5-6 | --- | --- | --- | |
| Command Code | 7-8 | alphanumeric | F | U |
| 9-10 | --- | --- | --- | |
| Response Code | 11-12 | binary | --- | A |
| Command ID | 13-16 | alphanumeric/ binary | --- | A |
| Database ID*** | 17-20 | numeric | F | U |
| 21-28 | --- | --- | --- | |
| Number of I/Os | 29-32 | binary | --- | A |
| 33-36 | --- | --- | --- | |
| Number of Commands | 37-40 | binary | --- | A |
| CPU Time | 41-48 | binary | --- | A |
| 49 | --- | --- | --- | |
| Command Option 2 | 50 | alphanumeric | F | U |
| 51-114 | --- | --- | --- | |
| Error Subcode | 115-116 | binary | --- | A |
| 117-144 | --- | --- | --- | |
| Command Time | 145-152 | binary | --- | A |
| User Area | 153-168 | not applicable | --- | U |
| --- | 169-193 | do not touch | --- | --- |
| ABD and Buffer | Before Adabas Call | After Adabas Call |
|---|---|---|
| Format * | ** | -- |
| Record * | F | U |
where:
| F | Supplied by user before Adabas call |
| A | Supplied by Adabas |
| U | Unchanged after Adabas call |
| * | Required only if user data to be stored |
| ** | Not used but should be included in Adabas call or one will be automatically generated. |
| *** | A database ID is only necessary if you are accessing a database other than the application's default database (read in by ADARUN DBID parameter, provided in the loaded link globals table, or linked with the link routine). |
| -- | Not used |
We recommend that you set unused ACBX fields to binary zeros before the direct call is initiated.
F2
CL
Adabas returns the response code for the command in this field. Response code 0 (ADARSP000) indicates that the command was executed successfully. Non-zero response codes, which can also have accompanying subcodes returned in the Error Subcode (ACBXERRC) field, are described in the Adabas Messages and Codes Manual documentation.
For ET logic users, Adabas returns the transaction sequence number of the user's last successfully executed transaction in this field. The number is provided in binary format.
Because the CL command includes an ET command (see Function and Use), it also increments the transaction sequence number by one (regardless of whether it completes a transaction with or without update commands). The incremented transaction sequence number is then returned.
The CL command returns binary zeros if it ends the session of an ET user without update commands.
Use this field to specify the database ID only if you are accessing a database other than the application's default database (read in by ADARUN DBID parameter, provided in the loaded link globals table, or linked with the link routine). The Adabas call will be directed to this database.
This field is a four-byte binary field, but at this time only two-byte database IDs are supported. Therefore, the database ID should be specified in the low-order part (rightmost bytes) of the field, with leading binary zeros.
If this field is set to binary zeros, the Adabas API uses either the database ID from the ADARUN cards provided in DDCARD input data or the default database ID value provided in the LNKGBLS module linked with or loaded by the link routine.
Adabas returns the number of I/O operations resulting from this session's Adabas calls in this field.
In this field, Adabas returns the number of commands issued by the user during the user session.
In this field, Adabas returns an estimate of the amount of processor time used by this user for Adabas command processing.
The time is provided in units of 1/4096 microseconds; therefore, the high-order word of this field contains the estimated processor time in units of 1.048576 seconds.
| Option | Description |
|---|---|
| E | Indicates that user data is to be stored in an Adabas system file. |
If the command returns a nonzero response code, this field contains a subcode defining the exact response code meaning. Response codes and their subcodes are defined in the Adabas Messages and Codes Manual documentation.
The following buffers apply to a CL command:
A format buffer is not used by the CL command, but should be included in the Adabas call. If this is an ACB interface direct call and a format buffer is not specified, a processing error will occur; ACB interface direct calls expect buffers to be specified in a set sequence. If this is an ACBX interface direct call and a format buffer is not specified, one will be automatically generated.
User data output from the command is stored in this buffer. The number of bytes actually stored is determined by the value specified in the record buffer length field. The data is retained only if you have issued an OP command in which a nonblank, unique user ID was provided. If so, the data is retained until you issue the next ET or CL command in which user data is provided. If a nonblank user ID was not provided, the data cannot be retrieved in a subsequent session.
