Session Pooling - IBM CICS Interface for Teradata

IBM CICS Interface for Teradata® Reference

Product
IBM CICS Interface for Teradata
Release Number
16.20
Published
October 2018
Language
English (United States)
Last Update
2018-10-10
dita:mapPath
yky1527114222324.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2448
lifecycle
previous
Product Category
Teradata Tools and Utilities

With respect to session pooling (having a pool of pre-logged on sessions), whenever an application transmits a logon request using a logon string that matches one in the established session pool, the application is assigned to one of the available sessions.

Assigning an application to an established session pool improves response time since the application’s logon request need not be sent to the Teradata Database. Once a transaction starts, subsequent calls to the Teradata Database use the pre-allocated sessions instead of repeating the logon procedure.

The transaction’s logon entry in the session pool exists until the program issues a LOGOFF request to the Teradata Database.

Then, all resources allocated to the transaction are released and returned to the session pool.

For detailed information on session pooling, see Teradata Director Program Reference (B035-2416).