Session Logoff Process - Teradata Director Program

Teradata Director Program Reference

Product
Teradata Director Program
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-09
dita:mapPath
hwt1488824663348.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2416
lifecycle
previous
Product Category
Teradata Tools and Utilities

The following process occurs when the application logs off the session.

  1. The Teradata Database is not notified that the session has been logged off.
  2. TDP removes the session from the in-use category and returns it to the not-in-use category.

    If a STOP POOL command (or a MODIFY POOL command to reduce the number of pool sessions) is entered while the session is in use, the session is logged off of the Teradata Database.

    If the database to be used by the application differs from the database associated with the logon string of the pool, the application must either change the default or fully qualify all table references.

  3. If an application either abends or a session logs off from a session pool, the system does a clean up as follows:
    • Deletes all spool files
    • Releases all locks
    • Reestablishes the default database

If an ENABLE POOL DETAIL command has been issued, messages indicate why a session is not satisfied from a session pool.

If an ENABLE POOL STATUS command has been issued, a TDP0802 message indicates if a session is satisfied from a session pool.

If an ENABLE POOL STATUS command has been issued, a TDP0803 message indicates if a session that had been satisfied from a session pool ends.