Logging Pool Sessions on to the Teradata System - Teradata Director Program

Teradata® Director Program Reference

Product
Teradata Director Program
Release Number
16.20
Published
September 2019
Language
English (United States)
Last Update
2019-10-11
dita:mapPath
xuf1527114222341.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2416
lifecycle
previous
Product Category
Teradata Tools and Utilities

The sessions in a pool are logged on to the Teradata Database once using the START POOL operator command (see START POOL) and remain logged on until they are explicitly logged off by the STOP POOL (or STOP POOL and LOGOFF POOL) operator commands.

When a pool is first established, all pool sessions are not in use. When an application sends a logon request whose logon string matches that of the session pool, as described below, the application is assigned an available session from the pool. This results in a “quick” logon, because the application’s logon request does not have to be sent to the Teradata Database.

The session assigned to the application is marked “in-use” and cannot be reassigned to another application until the current application logs off. The logoff returns the session to the pool, where it becomes available for use by another application.