SESSION SQLFLAG - Basic Teradata Query

Basic Teradata Query Reference

Product
Basic Teradata Query
Release Number
16.00
Published
November 2016
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
hyz1479325149183.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2414
lifecycle
previous
Product Category
Teradata Tools and Utilities

Purpose

Enables and disables the issue of warnings in response to syntax errors in accordance with Federal Information Processing Standards (FIPS) Publications 127-2 and 127-3 for ANSI compliance.

Syntax



where the following is true:

ENTRY
A warning is to be issued for syntax errors according to FIPS 127-2 tests.
INTERMEDIATE
A warning is to be issued for syntax errors according to FIPS 127-3 tests.
NONE
No warning is to be issued for violations of ANSI-compliant syntax.

Usage Notes

The SQLFLAG option takes effect at logon time. Before changing the SESSION SQLFLAG setting, all Teradata Database sessions must be logged off. Otherwise, the current setting remains in effect and BTEQ displays the following warning message:

*** Warning: You must not be logged on to change the SQLFLAG or TRANSACTION settings.

Example 1 – SQLFLAG

To enable warnings in response to syntax errors in accordance with FIPS 127-2, type:

.set session SQLFLAG ENTRY

Example 2 – SQLFLAG

To disable warnings of violations of ANSI-compliant syntax, specify the SESSION SQLFLAG command as:

.set session SQLFLAG NONE;

or

.set session SQLFLAG;
Both the SET and SESSION keywords can be omitted when using this command.

BTEQ Response

Unless BTEQ encounters an error condition, there is no display response to the SESSION SQLFLAG command.