Purpose
This control enables users to specify if warnings are to be issued in response to syntax errors in accordance with Federal Information Processing Standards (FIPS) Publications 127-2 and 127-3 for ANSI compliance.
Syntax
| Command | Shorthand | Command | Shorthand |
|---|---|---|---|
| SESSION | S | SQLFLAG | SF |
| Option | Shorthand | Option | Shorthand | Option | Shorthand |
|---|---|---|---|---|---|
| NONE | N | ENTRY | E | INTERMEDIATE | I |
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 database user 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.
The DEFAULTS command does not affect SESSION SQLFLAG setting.
The SESSION SQLFLAG command cannot be used in an SQL macro.
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;
BTEQ Response
Unless BTEQ encounters an error condition, there is no display response to the SESSION SQLFLAG command.