Logging Rules for Applications - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

Enable or disable logging for a utility by specifying a rule for the application name. The system logs information for any user that logs on under the application name. For example, to log all queries that result from a FastLoad job, submit:

BEGIN QUERY LOGGING ON APPLNAME= 'FASTLOAD';

DBQL first searches for a rule for an application name before searching for rules for the user and account.

Creating logging rules by application name allows control over certain utilities, such as load and unload utilities, regardless of what user/account that the application runs under. For example, if you run utilities under the same users and accounts that are used for interactive queries, creating logging rules for utilities allows you to specify minimal logging for utilities and more extensive logging for interactive users.

The application names you specify with the APPLNAME option are the names the system passes in the reserved query band UtilityName.

The following table lists the UtilityName strings.

DBS Protocol Utility Type Utility Name Value Deprecated?
FastExport Standalone FastExport FASTEXP Yes
Teradata Parallel Transporter EXPORT operator TPTEXP No
JDBC FastExport JDBCE No
FastLoad Standalone FastLoad FASTLOAD Yes
Teradata Parallel Transporter LOAD operator TPTLOAD No
JDBC FastLoad JDBCL No
Crashdumps Save Program (CSP) Save Dump CSPLOAD No
MultiLoad Standalone MultiLoad MULTILOAD Yes
Teradata Parallel Transporter UPDATE operator TPTUPD No
JDBC MultiLoad JDBCM No