Determining Session Username - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Workstation-Attached Systems

Product
Call-Level Interface Version 2
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
ggf1488824663364.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

Some mechanisms (for example, LDAP) may result in sessions being connected under a username different from the one indicated in the logon character sequence. If an application needs to determine the actual logged on username for a given session, it should use the extant QEPISU item of the DBCHQE service. This item was originally added for SSO in TTU 6.1.