1 – ALIAS
For information on SET ALIAS, type HELP SET_ALIAS.
2 – ALL_CONSTRAINTS
For information on SET ALL CONSTRAINTS, type HELP SET_ALL_
CONSTRAINTS.
3 – ANSI
For information on SET ANSI, type HELP SET_ANSI.
4 – CATALOG
For information on SET CATALOG, type HELP SET_CATALOG.
5 – CHARACTER_LENGTH
For information on SET CHARACTER LENGTH, type HELP SET_CHARACTER_
LENGTH.
6 – CONNECT
For information on SET CONNECT, type HELP SET_CONNECT.
7 – Control
For information on SET Control, type HELP SET_Control.
8 – CONTINUE_CHARACTER
Defines the continuation character for interactive SQL. By
selecting a seldom used character the database administrator
can avoid problems with the minus sign to use a continuation
character in scripts.
9 – CURRENCY_SIGN
Specifies the currency indicator to be displayed in output.
(SQL produces currency indicators in output when you specify the
dollar sign ($) edit string for the column. See the DATATRIEVE
HELP topic for more information on edit strings.)
If you do not specify an alternate character, the default is
either the dollar sign ($) or the value specified by the logical
name SYS$CURRENCY.
10 – DATE date number
Specifies the display format for date values.
You must enter a number for the date-number argument. This number
corresponds to numbers in the date format logical names listed in
tables in the OpenVMS run-time library documentation.
For example, LIB$DATE_FORMAT_006 is one of the logical names in
the table. The logical name specifies the format in which the
eighth day of May in the year 1957 would be displayed as 8 May
57. Note that the latter part of the logical name is the number
006.
If you wanted to specify the 8 May 57 format using the SET DATE
FORMAT statement, you would use the numeric part of the LIB$DATE_
FORMAT_006 logical name, 6. You do not have to enter any leading
zeros that the number might have.
If you do not specify a date format, the default is dd-mmm-yyyy.
11 – DATE_FORMAT
Specifies the display format for either date values, time values,
or both.
You must specify a numeric argument with the DATE and TIME
portions of the SET DATE FORMAT statement. This numeric argument
is the same as the numeric portion of certain OpenVMS Run-Time
Library formats. The formats are documented in the OpenVMS run-
time library documentation. (This statement only accepts numbers
that reference OpenVMS format date and time logical names; it
does not support the ANSI/ISO date and time data types.)
The SET DATE FORMAT DATE and SET DATE FORMAT TIME statements
change only the output for the date or time formats. If you want
to change the input format, use the logical name LIB$DT_INPUT_
FORMAT. You must run the command procedure SYS$MANAGER:LIB$DT_
STARTUP.COM before using any of the run-time library date-time
routines for input or output formats other than the default. The
LIB$DT_STARTUP.COM procedure also defines spellings for date and
time elements in languages other than English. See the OpenVMS
run-time library documentation for more information on LIB$DT_
INPUT_FORMAT.
12 – DEFAULT_CHARACTER_SET
For information on SET DEFAULT CHARACTER SET, type HELP SET_
DEFAULT_CHARACTER_SET.
13 – DEFAULT_DATE_FORMAT
For information on SET DEFAULT DATE FORMAT, type HELP SET_
DEFAULT_DATE_FORMAT.
14 – DIALECT
For information on SET DIALECT, type HELP SET_DIALECT.
15 – DICTIONARY
Changes your default repository path name to the path name you
specify.
16 – DIGIT_SEPARATOR
Changes the output displaying the digit separator to the
specified character. The digit separator is the symbol that
separates groups of three digits in values greater than 999. For
example, the comma is the digit separator in the number 1,000.
(SQL produces digit separators in output when you specify the
comma (,) edit string for the column. See the DATATRIEVE HELP
topic for more information on edit strings.)
You must enclose the digit-sep-char argument within single
quotation marks.
If you do not specify an alternate character, the default is
either the comma (,) or the value specified by the logical name
SYS$DIGIT_SEP.
17 – EDIT
Controls the size of the editing buffer that you create when you
use the EDIT statement with a wildcard as the argument.
o SET EDIT KEEP n
Tells SQL to save the previous n statements. For example,
assume you have specified SET EDIT KEEP 5. When you type EDIT
*, SQL places the previous five statements in the editing
buffer. The number you specify with SET EDIT KEEP is the
maximum number of statements you can recall with the EDIT
statement. The default is 20.
o SET EDIT NOKEEP
This statement is equivalent to SET EDIT KEEP 0. If you use
this form of the statement and you type EDIT or EDIT *, your
editing buffer will be empty. This form of the statement saves
system resources when you are running command files rather
than an interactive process.
o SET EDIT PURGE
This statement retains the value of the KEEP parameter but
purges all previous statements. As with SET EDIT NOKEEP, if
you use the SET EDIT PURGE statement and then EDIT or EDIT *,
your editing buffer will be empty. Unlike the SET EDIT NOKEEP
statement, however, SET EDIT PURGE causes SQL to accumulate
subsequent statements to place in the editing buffer when you
issue EDIT statements later in the interactive session.
18 – execute-clause
Syntax options:
EXECUTE
NOEXECUTE
NO EXECUTE
Instructs SQL whether to execute the data manipulation statements
you issue in an interactive SQL session.
You can use the NOEXECUTE option in conjunction with the
SET FLAGS to examine the estimated cost and access strategy
associated with a query. If you specify SET NOEXECUTE, SQL
displays the access strategies without executing the query. SQL
also allows you to specify NO EXECUTE (as two words); this has
the same meaning as NOEXECUTE.
If you do not specify EXECUTE or NOEXECUTE, the default is
EXECUTE.
The SET TRANSACTION statement is not executed when SET NO EXECUTE
is active. Start or declare a transaction prior to using SET NO
EXECUTE.
19 – FLAGGER_OFF
Disables all previously set flaggers indicating nonstandard
syntax. This is the default.
20 – FLAGGER
Syntax options:
FLAGGER ON
FLAGGER SQL89
FLAGGER SQL92_ENTRY
FLAGGER MIA
Controls the output of informational messages that indicate
nonstandard syntax, that is, extensions to the ANSI/ISO standard
syntax or the MIA standard syntax.
If you specify SET FLAGGER ON, which is the same as specifying
SET FLAGGER SQL92_ENTRY ON, SQL sends you an informational
message if you issue a subsequent interactive SQL statement that
contains syntax that is an extension to the ANSI/ISO standard.
If you specify SET FLAGGER MIA ON, SQL sends you an informational
message if you issue a subsequent interactive SQL statement that
contains syntax that is an extension to the MIA standard.
The flaggers are independent of each other and any combination of
flaggers can be set at one time.
The default is FLAGGER OFF if you do not explicitly set a flagger
on.
21 – FLAGS
For information on SET FLAGS, type HELP SET_FLAGS.
22 – HOLD_CURSORS
For information on SET HOLD CURSORS, type HELP SET_HOLD_CURSORS.
23 – IDENTIFIER_CHARACTER_SET
For information on SET IDENTIFIER CHARACTER SET, type HELP SET_
IDENTIFIER_CHARACTER_SET.
24 – KEYWORD_RULES
For information on SET KEYWORD RULES, type HELP SET_KEYWORD_
RULES.
25 – FEEDBACK
SET FEEDBACK ON is a synonym for the SQL SET DISPLAY NO ROW
COUNTER statement. SQL data manipulation statements such as
SELECT, DELETE, UPDATE, and INSERT will display the number of
affected rows. SET FEEDBACK n sets a limit value which turns on
feedback only if more than 'n' rows are displayed. SET FEEDBACK
0 is synonymous with SET FEEDBACK ON. SET FEEDBACK OFF is a
synonym for the SQL SET DISPLAY ROW COUNTER statement. SQL data
manipulation statements no longer display the count of affected
rows.
SQL> set feedback 2
SQL> select * from work_status;
STATUS_CODE STATUS_NAME STATUS_TYPE
0 INACTIVE RECORD EXPIRED
1 ACTIVE FULL TIME
2 ACTIVE PART TIME
3 rows selected
SQL> set feedback 4
SQL> select * from work_status;
STATUS_CODE STATUS_NAME STATUS_TYPE
0 INACTIVE RECORD EXPIRED
1 ACTIVE FULL TIME
2 ACTIVE PART TIME
26 – LANGUAGE
Specifies the language to be used for translation of month
names and abbreviations in date and time input and display. The
language-name argument also determines the translation of other
language-dependent text, such as the translation for the date
literals YESTERDAY, TODAY, and TOMORROW.
If you do not specify a language, the default is the language
specified by the logical name SYS$LANGUAGE. If you require
different language spellings, you must define the logical name
SYS$LANGUAGES in addition to SYS$LANGUAGE. You must run the
command procedure SYS$MANAGER:LIB$DT_STARTUP.COM after defining
SYS$LANGUAGES. For example:
$ DEFINE SYS$LANGUAGES FRENCH, GERMAN, SPANISH
$ RUN SYS$MANAGER:LIB$DT_STARTUP.COM
$ SHOW LOGICAL SYS$LANGUAGES
"SYS$LANGUAGES" = "FRENCH" (LNM$SYSTEM_TABLE)
$ SHOW LOGICAL SYS$LANGUAGE
"SYS$LANGUAGE" = "ENGLISH" (LNM$SYSTEM_TABLE)
If you do not define SYS$LANGUAGES, all translation routines
default to English. See the OpenVMS run-time library
documentation for more information on LIB$DT_STARTUP.COM.
The SET LANGUAGE statement does not affect the collating
sequences used for sorting and comparing data. The CREATE
COLLATING SEQUENCE statement specifies alternate collating
sequences.
27 – LINE LENGTH n LINESIZE n
Specifies an alternate line length for SQL output.
You must enter a number n to designate the line length. The
number n can be any number up to 65535 octets.
You can use the SET LINE LENGTH (or SET LINESIZE) statement to
specify an alternate width for output that you are sending to a
file or to an alternate output device.
28 – LITERAL_CHARACTER_SET
For information on SET LITERAL CHARACTER SET, type HELP SET_
LITERAL_CHARACTER_SET.
29 – LOGFILE quoted filespec
This statement allows the executing SQL script to save output to
an OpenVMS file.
Output from interactive SQL will be written to the file-spec
specified. If the "ECHO" logfile-option is used, in addition
to writing the output to the designated file, all commands
and errors generated by interactive SQL are also written to
SYS$OUTPUT. If the "NOECHO" logfile-option is used, output to
SYS$OUTPUT is disabled. All commands and errors generated by
interactive SQL are only written to the output file.
The SET LOGFILE is functionally equivalent to the SET OUTPUT
statement.
A SET LOGFILE command that does not specify a file is equivalent
to SET NOLOGFILE.
30 – NAMES
For information on SET NAMES, type HELP SET_NAMES.
31 – NATIONAL_CHARACTER_SET
For information on SET NATIONAL CHARACTER SET, type HELP SET_
NATIONAL_CHARACTER_SET.
32 – NOLOGFILE
Closes the current output file specified by a prior SET LOGFILE
(or SET OUTPUT command).
33 – NOOUTPUT
Suspends writing to the output file.
34 – NOVERIFY
Does not display indirect command files. The default setting is
the setting currently in effect for DCL commands. If you have
not explicitly changed the DCL setting to VERIFY, the default is
NOVERIFY.
35 – OPTIMIZATION_LEVEL
For information on SET OPTIMIZATION LEVEL, type HELP SET_
OPTIMIZATION_LEVEL.
36 – OUTPUT file spec
Names the target file for output. The default file extension is
.lis.
If you specify OUTPUT with a file name, SQL writes its output
to a log file that you specify. The log file contains both
statements and results. If you issue a SET OUTPUT statement,
output is also written to standard output which is usually the
terminal.
If you specify OUTPUT without a file name, SQL suspends writing
output to a log file, if any, and writes the output to the
standard output. In other words, the SET OUTPUT statement without
a file name is equivalent to the SET NOOUTPUT statement.
SQL displays certain items (such as the headings produced by
the SHOW statement) in boldface type on your terminal screen. In
log files, however, the boldface items are surrounded by escape
characters. You can ignore these escape characters, edit them
out of your log file, or set your terminal so that SQL does not
display characters in boldface type.
If you disable boldface type using the following DCL command,
your log file will not contain escape characters:
$ SET TERM/NOANSI_CRT
37 – PAGE LENGTH n PAGESIZE n
Sets the size of a page in SQL help.
The following notes apply to the PAGE LENGTH (or PAGESIZE)
clause:
o The integer value must be a value between 10 and 32767.
o SET PAGE LENGTH (or SET PAGESIZE) can be used to effectively
disable the paging performed by help by setting the length to
a high value such as 32000.
o The page length is automatically set upon entry to interactive
SQL and is based on the OpenVMS terminal setting for this
session.
o The SHOW DISPLAY command can be used to view the currently
defined page length.
38 – QUOTING_RULES
For information on SET QUOTING RULES, type HELP SET_QUOTING_
RULES.
39 – RADIX_POINT
Changes the output displaying the radix point to the specified
character. The radix point is the symbol that separates units
from decimal fractions. For example, in the number 98.6, the
period is the radix point.
You must enclose the radix-char argument within single quotation
marks.
If you do not specify an alternate character, the default is
either the period (.) or the value specified by the logical name
SYS$RADIX_POINT.
40 – SCHEMA
For information on SET SCHEMA, type HELP SET_SCHEMA.
41 – sql-plus-options
These statements are provided for use with SQL*Plus scripts that
are run against Oracle Rdb.
Table 1-5 Supported SQL*Plus SET statements
SQL*Plus command Equivalent Oracle Rdb statement
SET ECHO ON SET VERIFY
SET ECHO OFF SET NOVERIFY
SET HEADING ON SET DISPLAY QUERY HEADER
SET HEADING OFF SET DISPLAY NO QUERY HEADER
SET FEEDBACK ON SET DISPLAY ROW COUNTER
SET FEEDBACK OFF SET DISPLAY NO ROW COUNTER
SET NULL SET DISPLAY DEFAULT NULL STRING
SET NULL 'literal' SET DISPLAY NULL STRING 'literal'
42 – TIME time number
Specifies the display format for time values.
You must enter a number for the time-number argument. This number
corresponds to numbers in the time-format logical names listed in
tables in the OpenVMS run-time library documentation.
For example, the table contains the logical name
LIB$TIME_FORMAT_020. The logical name specifies the format in
which the eighth hour, fourth minute, and thirty-second second of
a day would be displayed as 8 h 4 min 32 s. Note that the latter
part of the logical name is the number 020.
If you wanted to specify the 8 h 4 min 32 s format for the SQL
SET DATE FORMAT TIME statement, you would use the numeric part
of the LIB$TIME_FORMAT_020 logical name, 20. You do not have to
enter any leading zeros that the number might have.
If you do not specify a time format, the default is hh:mm:ss.cc.
43 – TIMING
The SET TIMING statement enables a single line report of used CPU
and Elapsed time for each successful SQL statement or command.
SQL> start transaction;
SQL> set timing on;
SQL> select count(*)
cont> from employees
cont> inner join job_history using (employee_id)
cont> inner join salary_history using (employee_id)
cont> inner join departments using (department_code)
cont> inner join jobs using (job_code)
cont> left outer join resumes using (employee_id)
cont> left outer join degrees using (employee_id)
cont> left outer join colleges using (college_code)
cont>
cont> ;
3871
1 row selected
Timing: Elapsed: 0 00:00:00.82 Cpu: 0 00:00:00.16
SQL> set timing off;
SQL> commit;
44 – TRANSACTION
For information on SET TRANSACTION, type HELP SET_TRANSACTION.
45 – VERIFY
Displays indirect command files at your terminal as you run them.
46 – VIEW_UPDATE_RULES
For information on SET VIEW UPDATE RULES, type HELP SET_VIEW_
UPDATE_RULES.
47 – WARNING
Syntax options:
WARNING DEPRECATE
WARNING NODEPRECATE
Specifies whether or not interactive SQL displays diagnostic
messages when you issue statements containing obsolete SQL
syntax. Deprecated or obsolete syntax is syntax that was allowed
in previous versions of SQL but has been changed. Oracle Rdb
recommends that you avoid using such syntax because it may not
be supported in future versions. By default, SQL displays a
warning message after any statement containing obsolete syntax
(SET WARNING DEPRECATE).
If you specify SET WARNING NODEPRECATE, SQL does not display any
messages about obsolete syntax.