Version 8.2.1
 —  Adabas Transaction Manager Operations Guide  —

Client Sessions


Client Session Identification using Communication IDs

Adabas Transaction Manager identifies a client session by its 28-byte Communications ID.

If a client issues Adabas commands under different Communications IDs, ATM regards these commands as having been issued by different clients. For example, this could occur during dynamic transaction routing in a CICS environment if the Adabas System Coordinator is not being used to manage the client sessions.

If the same Communications ID is to be used consecutively in more than one client environment (for example, CICS and batch), the first session must be terminated cleanly before the second is started.

Top of page

Client Session Memory Requirements

Note:
For information about the client-related memory requirements of the Adabas System Coordinator in the application address space, refer to the Adabas System Coordinator documentation.

The additional memory requirement per client session for the Adabas Transaction Manager client proxy is approximately:

The memory management functions of the Adabas System Coordinator might perform some upward rounding when it allocates memory for use by the Adabas Transaction Manager client proxy, so the actual memory usage per user could be greater than indicated by the above estimate.

Bear in mind that certain settings of the Natural ADAMODE parameter cause Natural to execute two sessions in parallel for each terminal user. This increases the effective number of clients in the client address space.

A syncpoint operation that occurs under the CICS RMI when an ET,BT,OP or CL command is issued, is handled under a shadow User ID, associated with the original user. This, too, effectively increases the number of active clients in the CICS address space, though these internal clients are short-lived.

Top of page