Additional information available:

$@ALTERATTACHBEGIN_DECLARECLOSE
COMMENT_ONCOMMITCONNECTCREATEDBKEYDECLARE
DELETEDESCRIBEDISCONNECTDROPEDITEND_DECLARE
EXECUTEEXECUTE_IMMEDIATEEXITEXPORTFETCHFINISH
GRANTHELPIMPORTINCLUDEINSERTINTEGRATE
LSENULLOPENPREPAREPRINTQUITRELEASE
REVOKEROLLBACKRUN_TIME_ONLY_KITSELECTSETSET_ALIAS
SET_ALL_CONSTRAINTSET_ANSISET_CATALOGSET_CONNECT
SET_SCHEMASET_TRANSACTIONSHOWSQLCASQLDA
UPDATEUSERWHENEVER

aliasarith expressionauthorization idcol select expr
Command recallcorrelation namedatabase handleData Distributor
data typesDCL invokedefault databaseDynamic SQLDyn DECLARE CURSOR
Dyn FETCHDyn INSERTDyn OPENErrorExecute(@)Ext Dyn DEC CURSOR
FunctionsGRANT ANSI styleInteractive kitLinking programs
literalsModule languageNew featuresPrecompilerpredicateRelease Notes
REVOKE ANSI styleSample Databasesselect exprsingleton select
Value expression

 An alias is a name that identifies a particular attachment to a
 database so that your program or interactive SQL statements can refer
 to more than one database.

 You can specify the alias in an ATTACH, CONNECT, CREATE DATABASE or
 DECLARE ALIAS statement.  (Specify an alias in addition to the file
 specification or a data dictionary path name that you supply in these
 statements.) An alias must be no longer than 25 characters.

 Once you specify an alias, you must use it when referring to the
 database in subsequent SQL statements (unless those statements are
 within a CREATE DATABASE statement).  You must use an alias when you
 declare more than one database.

 DIGITAL proprietary database languages (such as RDO in Rdb/VMS) use
 the term database handle instead of alias.  The two terms mean the
 same thing.

Additional information available:

Examples

 Example 1:  Qualifying domain names

 This example attaches to a PERSONNEL database by the alias CORPORATE
 and creates a domain within PERSONNEL.  When you create a domain for
 a database that you have attached to using an alias, you must qualify
 the domain name with that alias.

 SQL> ATTACH 'ALIAS CORPORATE FILENAME DISK01:[DEPT3]PERSONNEL';
 SQL> CREATE DOMAIN ADDRESS_DATA2_DOM CHAR(20) DEFAULT NULL;
 %SQL-F-NODEFDB, There is no default database
 SQL> CREATE DOMAIN CORPORATE.ADDRESS_DATA2_DOM CHAR(20) DEFAULT NULL;
 SQL> SHOW DOMAINS;
 User domains in database with alias CORPORATE
 ADDRESS_DATA2_DOM               CHAR(20)
 SQL>
 Example 2:  Qualifying catalog names in a multischema database

 When you use the alias to qualify the name of a catalog, you must
 separate the alias from the catalog name with a period and use double
 quotation marks to delimit the name pair, as follows:

 SQL> SET ANSI QUOTING ON;
 SQL> SHOW DOMAIN "CORPORATE.MARKETING".DEPT1.LAST_NAME;

 An arithmetic expression is a value expression formed by combining
 value expressions with arithmetic operators.  When you use an
 arithmetic expression in a statement, SQL calculates the value
 associated with the expression and uses that value when executing the
 statement.  Therefore, an arithmetic expression must be reducible to
 a value.

 If either operand of an arithmetic expression is a null value, the
 resulting value is also null.

 Select More_Information to continue.

Additional information available:

Date and time arithmeticMore Information

 The list of legal date arithmetic operations and their results
 follows:

 Operand1     Operator        Operand 2    Result Type

 date-time      - (subtract)  date-time     interval
 date-time      + or -        interval      date-time
 interval       +             date-time     date-time
 interval       + or -        interval      interval
 interval       * or /        numeric       interval
 interval       /             numeric       interval
                - (negate)    interval      interval

 The arithmetic operators and their functions are:

 +       Add
 -       Subtract
 *       Multiply
 /       Divide

 You can use parentheses to control the order in which SQL performs
 arithmetic operations.  SQL follows the normal rules of precedence.
 That is, it evaluates arithmetic expressions in the following order:

 1.  Value expressions in parentheses

 2.  Multiplication and division, from left to right

 3.  Addition and subtraction, from left to right

 When you issue a CREATE SCHEMA statement (alone or as part of a
 CREATE DATABASE statement), you must specify either a schema name or
 an authorization identifier.  If you wish to comply with the ANSI/ISO
 standard, you must specify an authorization identifier.

 An authorization identifier is a user name that SQL uses for
 privilege checking when you specify ANSI_AUTHORIZATION in the
 precompiler or module language command line options.  Under ANSI
 privilege checking, SQL restricts access to the schema to that user
 whose user name matches the authorization identifier.

 col-select-expr =

 -+-+-> col-select-clause -+-+--------------------+-+
  | +->( col-select-expr )-+ +-> order-by-clause -+ |
  | +---------<------------+                        |
  | +-> UNION -+-------+----+                       |
  |            +> ALL -+    |                       |
  +--------<----------------+                       |
  +-------------------------------------------------+
  +-+--------------------+--------------------------->
    +-> limit-to-clause -+

Additional information available:

UNION

col select clauseMore Information

 col-select-clause =

 SELECT -+------>------+-+-> * -----------------------------+ FROM +
         +-> ALL ------+ +-> table-name -------+-> .* ------+      |
         +-> DISTINCT -+ +-> view-name --------+            |      |
         |               +-> correlation-name -+            |      |
         |               +-> value-expr --------------------+      |
         ++------+-+---> SUM ---++-> (DISTINCT column-name) +      |
          +-> + -+ +---> AVG ---++-> (ALL value-expr) ------+      |
          +-> - -+ +---> MAX ---+                           |      |
                   +---> MIN ---+                           |      |
                   +---> COUNT -+--> (*) -------------------+      |
                                +--> (DISTINCT column-name) +      |
   +--------------------------------<------------------------------+
   +++-> table-name ++--------------------++-+-------->-----------++
    |+-> view-name -++-> correlation-name +| +-> WHERE predicate -+|
    +---------- , <------------------------+                       |
   +------------------------------<--------------------------------+
   ++------------->------------------+-+---------->----------+-->
    +-> GROUP BY -+-> column-name -+-+ +-> HAVING predicate -+
                  +------- , <-----+

 The UNION operator merges the results of a select expression or
 select clause with another select expression or select clause into
 one result table by appending the values of columns in one table with
 the values of columns in other tables.

Additional information available:

ALL

 The ALL qualifier specifies that duplicate rows should not be
 eliminated from the result table.

 A column select expression is a select expression that specifies a
 one-column result table.  Column select expressions cannot specify a
 list of select items.

 SQL accepts a column select expression as a type of value expression.
 However, since a value expression must correspond to a single value,
 a column select expression used as a value expression should not
 return more than one value.  If it does, SQL generates an error.  A
 column select expression used as a value expression cannot include
 GROUP BY or HAVING clauses.

                                 NOTE

         IN predicates allow column select expressions used as
         value expressions to return more than one value.


 Column select expressions are also called subqueries.

 Interactive SQL users can recall the 20 most recent command lines
 using the up and down arrow keys or the CTRL/B key sequence:

  o  The up arrow key recalls lines in sequence from most recent to
     least recent.

  o  The CTRL/B key sequence also recalls lines in sequence from most
     recent to least recent.

  o  After you have recalled prior lines, the down arrow key allows
     you to recall more recently entered lines.

 A qualifier for column names.  Users can qualify a column name with
 its table or view name, or with an aribitrary correlation name they
 specify in the FROM clause of an SQL statement.  SQL requires
 correlation names as qualifiers instead of table or view names in
 statements that join a table with itself.

 DIGITAL proprietary database languages (such as RDO in Rdb/VMS) use
 the term database handle instead of alias.  The two terms mean the
 same thing.  For more information see the Help topic on alias.

 VAX Data Distributor is a software product that enables you to make
 data available to users and applications at multiple sites in a
 network.  From a source relational database, you can define the
 following transfers:

  o  Transfer an entire source database or a subset of that database.
     Transfers can remain on the same processor or you can define
     transfers to remote processors.

  o  Transfer data from multiple source databases into a single target
     database.

  o  Transfer data from one or more source databases into an existing,
     user-created target database.

Additional information available:

CREATE_SCHEDULECREATE_TRANSFERDROP_SCHEDULEDROP_TRANSFER
REINITIALIZESHOW_TRANSFERSTART_TRANSFERSTOP_TRANSFER

More InformationRelease NotesError msg doc

 Data Distributor allows three types of transfer:  extraction,
 extraction rollup, and replication transfers.

 Extraction transfers copy the latest version of the tables specified
 in the transfer definition from a single source database to a target
 database.  Once the transfer completes, Data Distributor severs the
 connection between the source and target databases.

 Extraction rollup transfers copy the latest version of the tables
 specified in the transfer definition from multiple source databases
 to a target database.  Once the transfer completes, Data Distributor
 severs the connection between the source and target databases.

 Like extraction transfers, a replication transfer creates tables at a
 target site during initial execution.  Unlike extraction transfers, a
 replication transfer maintains a connection with the target database
 so that the source database can supply updates to the target.  After
 the initial transfer execution, subsequent executions of a
 replication transfer involve only those additions, modifications, and
 deletions that have been made to rows in the source database since
 the previous transfer.

 You can issue Data Distributor statements, options, and qualifiers
 from SQL when VAX Data Distributor is installed on your system.  See
 the VAX Data Distributor Handbook and the SQL Reference Manual for
 details of the Data Distributor statements.

 To see the current Release Notes for VAX Data Distributor, type or
 print the following file:

     SYS$HELP:DDALvvu.RELEASE_NOTES

         where    vv = version
                  u  = update

 For example:

     SYS$HELP:DDAL022.RELEASE_NOTES

 Errors returned by Data Distributor are documented online in the file
 SYS$HELP:DDAL$MSG.DOC, which you can PRINT, TYPE, or SEARCH at DCL
 level.

 CREATE SCHEDULE FOR ---> transfer-name -+
  +--------------------------------------+
  ++----------->---------------------+---+
   +-> START -----> start-date-time -+   |
  +--------------------------------------+
  ++----------->-----------------------+-+
   +-> EVERY -+> every-delta-time ----++ |
              +> every-absolute-time -+  |
  +--------------------------------------+
  ++--------------------------------------+->
   +> RETRY -> count -> TIMES ------+     |
       +----------------------------+     |
       +-+------------------------------+-+
         +-> RETRY EVERY -> delta-time -+

Additional information available:

More Informationtransfer-namestart-date-timeevery-delta-time
every-absolute-timeAT at-timecountdelta-timeExamples

 Creates a schedule definition and stores it in the transfer database.
 The schedule definition specifies when and how often a transfer
 should execute.  A transfer can have only one schedule definition
 associated with it.  Data Distributor returns an error if you attempt
 to create a schedule for a transfer that already has one.

 Names the transfer for which this schedule is being defined.  The
 transfer must already exist before a schedule definition can be
 created for it.

 Specifies the time to execute the initial transfer.  You can specify
 a delta time or an absolute time.  If you use a delta time, Data
 Distributor uses the current time and the delta-time value to
 calculate the actual transfer time.  If you supply an absolute time,
 the initial transfer will be executed at the time specified.  The
 START clause is optional.  If you do not include a START clause, the
 start time is set to the current time.  The transfer then will
 execute as soon as the transfer schedule definition is processed.

 The delta-time format is as follows:

 dddd hh:mm:ss.cc

 The absolute-time format is as follows:

 dd-mmm-yyyy hh:mm:ss.cc

 In the delta-time and absolute designations, the abbreviations have
 the following meanings:

  o  dddd - Number of days

  o  dd - Day of the month

  o  mmm - Month

  o  yyyy - Year

  o  hh - Hours

  o  ss - Seconds

  o  cc - Hundredths of a second

 Used to calculate the time to execute the next transfer.  The EVERY
 clause is optional.  If you specify the EVERY clause, you must
 specify either every-delta-time or every-absolute-time.  If you omit
 the EVERY clause, the transfer occurs only once.The valid
 specification for every-delta-time is the delta-time format used by
 the $BINTIM VMS system service.

 every-absolute-time =

 --+--> DAY ----+-+------->----------+--+->
   +--> WEEK ---+ +-> AT -> at-time -+  |
   +--> MONTH --+                       |
   ++-> weekday --+------->----------+-++
    |             +-> AT -> at-time -+ |
    +------------ , <------------------+

 Used to calculate the time to execute the next transfer.  The EVERY
 clause is optional.  If you specify the EVERY clause, you must
 specify either every-absolute-time or every-delta-time.  If you omit
 the EVERY clause, the transfer occurs only once.

 Valid specifications for the every-absolute-time parameter are:

  o  DAY

     The transfer executes on a daily basis.

  o  WEEK

     The transfer occurs every week on the same day of the week as the
     initial transfer.

  o  MONTH

     The transfer occurs on a monthly cycle on the same day of the
     month as the initial transfer.

  o  WEEKDAY

     The transfer executes on the weekdays that you list.  If you list
     more than one weekday, separate the days with commas.  Valid
     weekdays are SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY,
     FRIDAY, and SATURDAY.

 Qualifies every-absolute-time by specifying the time of day the
 transfer should occur.  If you specify DAY, WEEK, or MONTH, but do
 not specify an at-time, Data Distributor uses the time of day of the
 initial transfer.  You can specify in a list of weekdays the at-time
 for each day.  If you omit the at-time for any weekday, Data
 Distributor selects as the default the time used for the previous
 entry in the list.  For the first entry in the list, the time of day
 of the initial transfer is used, if none is specified.

 The at-time argument has the following format:  hh:mm:ss.cc.  For an
 explanation of these abbreviations, see the Help topic on
 start-date-time.

 Specifies the maximum number of times Data Distributor retries a
 transfer if a transfer execution fails.  If you do not include a
 retry count or if the count value is set to zero, Data Distributor
 does not attempt to retry the transfer until the next scheduled
 transfer time as indicated by the EVERY clause.  If you include a
 retry count and the transfer fails, the retry will start at the
 beginning, not where the transfer left off.

 Specifies the length of time Data Distributor waits between the time
 of the last failed attempt and the time of the next retry attempt.
 The RETRY EVERY delta-time clause is optional and can only be
 specified if the RETRY count TIMES clause is included.

 Example 1:  Creating a schedule to run a transfer once a week

 This example calls for the COLLEGE_INFO transfer to execute at 3:00
 pm.  every Wednesday.  The schedule definition calls for a maximum of
 three retries occurring at intervals of 30 minutes.

 SQL> CREATE SCHEDULE FOR COLLEGE_INFO
 cont>  START 14-NOV-1990 15:00:00.00
 cont>     ! Wednesdays at 3 p.m.
 cont>     EVERY WEDNESDAY AT 15:00:00
 cont>     RETRY 3 TIMES
 cont>     RETRY EVERY 0 00:30:00
 cont>  ;

 Example 2:  Creating a schedule to run a transfer on an as-needed
 basis

 In this example, a transfer starts at midnight on December 15.
 Because the transfer will be performed on an as-needed basis, the
 user does not include an EVERY clause.  The user can replace the
 schedule definition if the transfer has to be run on a firm schedule
 at some later date.

 SQL> CREATE SCHEDULE FOR NH_EVALUATION
 cont>   START 15-DEC-1990
 cont>  ;

 CREATE TRANSFER --> transfer-name --> TYPE IS +
 +---------------------------------------------+
 ++> REPLICATION -> replication-extr-move-clause -++
  +> EXTRACTION -> replication-extr-move-clause --+|
  +> EXTRACTION ROLLUP -> rollup-move-clause -----+|
  +------------------------------------------------+
  +-> to-clause -+----------------------------+----+
                 ++> target-db-param-clause -++    |
                  +------------<-------------+     |
  +------------------------------------------------+
  ++----------------------------------+------------+
   +-+> transfer-file-options-clause ++            |
     +-------------<-----------------+             |
  +------------------------------------------------+
  ++-------------------+--------------------------> ;
   +-> comment-clause -+

Additional information available:

TYPE_ISREPLICATIONEXTRACTIONEXTRACTION_ROLLUP

More Informationtransfer-namereplication-extrrollup-move-clause
to-clausetarget-db-paramtransfer-filecomment-clauseExamples

 Creates a transfer definition and stores it in the transfer database.
 A transfer definition contains all of the information necessary to
 select a set of records from the source database and to define a
 target database.  A transfer definition also can contain the views to
 be defined on the target database and the command procedures to be
 executed before and after the execution of the transfer.

 Additionally, you can specify the following in a transfer definition:

  o  Whether the target database already exists or whether Data
     Distributor must create a new target database

  o  New names for specified data definitions in the target database

 Identifies the transfer by name.  The transfer name must be unique
 among the set of all transfers defined in the transfer database.
 Because a single transfer database serves all nodes in a VAXcluster
 environment, the transfer name must be unique across all nodes at a
 given VAXcluster site.  The transfer name does not have to be unique
 within the entire communications network.  Two VAXcluster systems can
 define transfers using the same transfer name.  If each transfer
 specifies the same existing target database, the transfers are
 differentiated by their respective network location.

 Names the type of transfer for the transfer definition.  REPLICATION,
 EXTRACTION, and EXTRACTION ROLLUP are the three valid transfer types
 for Data Distributor.

 Declares the transfer type to be a REPLICATION transfer.

 When a replication transfer executes, Data Distributor creates the
 tables at the target site during the initial execution and maintains
 a connection to that target database so the source can supply updates
 to the target database.  Subsequent transfers involve only those
 additions, modifications, and deletions that have been made to the
 selected rows in the source database.

 If the target and source databases become inconsistent with each
 other, you can use the REINITIALIZE TRANSFER statement and then the
 START TRANSFER statement to create new versions of the target tables
 that are consistent with the source tables.

 Declares the transfer type to be an EXTRACTION transfer.

 The tables copied to a target database by an extraction transfer
 maintain no relationship with the source database tables.  Unlike a
 replication transfer, Data Distributor severs the connection between
 the source database and the target database after the extraction
 transfer completes.  Each time an extraction transfer executes, Data
 Distributor copies the latest version of the selected tables to the
 target database.

 Although you can write to tables created by Data Distributor in a
 target database, any future execution of an extraction transfer that
 copies the same tables from the source database will not include data
 written only to the target tables.  For more information on read and
 write restrictions, see the description of the to-clause.

 replication-extr-move-clause =

 ----> MOVE TABLES --+-> move-tables-clause -+-+-----------------------+-->
                     +---------- , <---------+ +-> move-views-clause --+

 Selects the rows of a table that Data Distributor transfers to the
 target database during an extraction or a replication transfer.  The
 rows selected for replications are specified with a restricted form
 of a select clause.  You must specify a move-tables-clause for each
 user table moved to the target database.

Additional information available:

MOVE_TABLES

move-tables-clausemove-select-clauseselect-listpredicatemove-views-clause

 For extraction transfers, specifies the table name or view name that
 you want copied from the source database.  For replication transfers,
 specifies the table name (not view name) that you want copied from
 the source database.  If you do not specify a table name or view
 name, you can specify a select clause.

 move-tables-clause =

 ---+--+---------------------+--+--- * ------------+--+--+
    |  +--> alias ----> . ---+  +--> table-name ---+  |  |
    |  |                        +--> view-name ----+  |  |
    |  +---------->----------------> "*.*".*.* ----+  |  |
    +--> move-select-clause --------------------------+  |
    +----------------------------------------------------+
    +----------------+--------------------+------------>
                     |                    |
                     +-> INTO table-name -+

 move-select-clause =

 --> SELECT -+-------------+--> select-list --> FROM -+-------------------+--+
             +-> ALL ------+                          +-> alias ----> . --+  |
             +-> DISTINCT -+                                                 |
                                                                             |
 +---------------------------------------------------------------------------+
 |
 +--+--> table-name ---+--+--------->-----------+-+------->---------------+->
    +--> view-name ----+  +-> correlation-name -+ +-> WHERE predicate  ---+

 select-list  =

 ---+------> * -----------------------------------------+->
    +-+-+--> column-name --+---------------------------++
      | +------- , <-------+                           |
      +-+-> select-element-list -+--> .* -------------++
        |                        +--> .column-name -+-+
        +------------------- , <--------------------+

 select-element-list =

 ---+--> table-name -------+->
    +--> view-name --------+
    +--> correlation-name -+

 predicate  =

 ---+--+----------+--+---> basic-predicate ------------+---+--->
    |  +--> NOT --+  +---> between-predicate ----------+   |
    |                +---> containing-predicate -------+   |
    |                +---> in-predicate ---------------+   |
    |                +---> like-predicate -------------+   |
    |                +---> null-predicate -------------+   |
    |                +---> starting-with-predicate ----+   |
    |                +---> (predicate) ----------------+   |
    |                                                      |
    +--------------------+-- AND <--+----------------------+
                         +--- OR <--+

 move-views-clause =

 MOVE VIEWS ---+
     +---------+
     ++-+------>--------+> * -----------+--------->----------+->
      | +-> alias --> . +               |                    |
      | +------>----------> "*.*".*.* --+                    |
      +-+-+---->---------+> view-name -+------->---------+-+-+
        | +-> alias -> . +             +> INTO view-name + |
        +------------------- , <---------------------------+

 Specifies that Data Distributor create an extraction rollup database
 at the target site by transferring selected tables and columns from
 one or more source databases into a single target database.  An
 extraction rollup database is created at the target site, and Data
 Distributor reads data from the source databases and stores the data
 in a target database.

 Each time an extraction rollup transfer is executed, Data Distributor
 creates a new version of the target database and transfers a complete
 copy of the selected rows to the target database.  Upon completion of
 an extraction rollup transfer, Data Distributor severs the connection
 between the source database or databases and the target database.

 rollup-move-clause =

 ----> MOVE TABLES --+--> rollup-source-table-spec ---+--->
                     +------------- , <---------------+

Additional information available:

More Informationrollup-sourcemove-select-expr

 Selects the tables or views that Data Distributor transfers to the
 target database from a number of source databases during an
 extraction rollup transfer.  You can roll up multiple tables into a
 single target table only by using a move select expression with the
 UNION ALL keywords.

 Rollup-move-clause has the following restrictions:

  o  Data Distributor requires you to declare each source database
     with a different alias.  You must then use these aliases in the
     rollup-move-clause clause.

  o  The rollup-move-clause clause must be used with the EXTRACTION
     ROLLUP parameter.

  o  The rollup-source-table-spec clause that specifies *.* expands to
     a comma-separated list of alias.* for each declared database.
     The order of the list is undefined.

  o  All move-select-clause clauses that include the UNION keyword
     must also include the ALL keyword, must be of the same degree,
     and must match data types exactly for all columns being merged.

 rollup-source-table-spec =

 --+--> *.* --------------------------------------+->
   +--> alias ------> . --+-> * -----------------++
   |                      +-> table-name --+-+   |
   |                      +-> view-name ---+ |   |
   +--> move-select-expr --------------------+-+ |
   +-------------------------------------------+ |
   +--> INTO table-name -------------------------+

 move-select-expr =

 ---+--> move-select-clause --+-->
    +------- UNION ALL <------+

 to-clause =

 -> TO -+-> NEW FILENAME -> target-file-spec ------------+>
        +-> EXISTING -+-> ALIAS alias ---------------++  |
                      +-> FILENAME target-file-spec -+|  |
                   +----------------------------------+  |
                   +-+----------------------+------------+
                     +-> WITH CHECKING -----+
                     +-> WITH NO CHECKING --+

Additional information available:

More Information

 Specifies the name of an existing target database or the name of a
 new target database to be created by Data Distributor.

 target-db-param-clause =

 ---+-+->----------------------------------------------------+-+-->
    | +-> ALLOCATION IS --------> number-pages --> PAGES ----+ |
    | +-> PAGE SIZE IS ---> page-blocks ------> BLOCKS ------+ |
    | +-> NUMBER OF BUFFERS IS --> number-buffers -----------+ |
    | +-> NUMBER OF USERS IS ----> number-users -------------+ |
    | +-> BUFFER SIZE IS --> buffer-blocks ---> BLOCKS ------+ |
    | +-> EXTENT IS -------+-> extent-pages ---> PAGES ---+--+ |
    | |                    +-> (extension-options) -------+  | |
    | +-> SNAPSHOT IS ----+-> ENABLED -+->-------------+-+---+ |
    | |                   |            +-> IMMEDIATE --+ |   | |
    | |                   |            +-> DEFERRED  --+ |   | |
    | |                   +-> DISABLED ------>-----------+   | |
    | +-> SNAPSHOT ALLOCATION IS --> snp-pages --> PAGES ----+ |
    | +-> SNAPSHOT EXTENT IS -+-> extent-pages --> PAGES --+-+ |
    |                         +-> (extension-options) -----+   |
    +------------------<--------------------------<------------+

Additional information available:

More Informationextension-options

 Specifies values for parameters that Data Distributor uses to create
 the target database.  This clause uses syntax similar to the SQL
 CREATE DATABASE statement.  However, Data Distributor does not
 support all the parameters that the SQL CREATE DATABASE statement
 does.

 extension-options =

   -----> MINIMUM OF --> min-pages ---> PAGES ---> , -+
     +------------------------------------------------+
     +--> MAXIMUM OF --> max-pages ---> PAGES ---> , -+
     +------------------------------------------------+
     +--> PERCENT GROWTH IS ---> growth ---->

 transfer-file-options-clause

   -+-+------------------------->---------------------------+------->
    | +--> PROLOGUE FILE IS ----> prologue-file-spec -------+
    | +--> NO PROLOGUE --------->---------------------------+
    | +--> EPILOGUE FILE IS ----> epilogue-file-spec -------+
    | +--> NO EPILOGUE --------->---------------------------+
    | +--> LOG FILE IS ---------> log-file-spec ------------+
    | +--> NO LOG -------------->---------------------------+
    +---------------------------<---------------------------+

Additional information available:

More Information

 Specifies the DCL command procedures to be executed before or after a
 transfer runs, and the VMS file where logging information related to
 the transfer execution is located.  For each transfer definition, you
 can specify one prologue file, one epilogue file, and one log file,
 or any combination of the three.

 comment-clause =

 ----> COMMENT IS --+--> string-literal ---+--->
                    +--------- , <---------+

Additional information available:

More Information

 Documents your transfer definition with one or more character string
 literals.

 Example 1:  Creating a local extraction database from a remote node

 This example shows an extraction from a remote source database to a
 local target database.  The CREATE TRANSFER statement specifies the
 transfer of all personnel rows to the target node.

 SQL> ATTACH 'FILENAME NODE1::DISK1:[DIR1]PERSONNEL';
 SQL> CREATE TRANSFER PERS_EXAMP TYPE IS EXTRACTION
 cont>  MOVE TABLES *
 cont>  TO NEW FILENAME [LEARNER.PERS]PERS_COPY
 cont>  LOG IS [LEARNER.PERS]PERS_EXAMP.LOG
 cont>  COMMENT IS 'Extraction of personnel information'
 cont>  ;

 Example 2:  Creating an extraction database on a remote node from a
 source remote node

 This example shows an extraction transfer from a remote source to a
 remote target database.  The log file, PERS_REC.LOG, is located on
 the source node where the transfer definition was defined.
 SQL> ATTACH 'FILENAME NODE1::DISK1:[DIR1]PERSONNEL';
 SQL> CREATE TRANSFER PERS_REC TYPE IS EXTRACTION
 cont>  MOVE TABLES *
 cont>  TO NEW FILENAME NODE2::DISK2:[PROTO]PERS_REC_TARGET
 cont>  LOG IS USER3:[DBS.PERSLOG]PERS_REC.LOG
 cont>  COMMENT IS 'Extraction of personnel information'
 cont>  ;

 DROP SCHEDULE FOR ---> transfer-name ----> ;

Additional information available:

More Informationtransfer-nameExample

 Deletes the schedule definition associated with a transfer
 definition.  You can delete a schedule definition only when the
 associated transfer is in the suspended state.  (Refer to the STOP
 TRANSFER statement for information about how to suspend a transfer.)
 If you issue a START TRANSFER statement after deleting the schedule,
 the transfer will be placed in the unscheduled state.

 Identifies the transfer whose schedule is to be deleted.

 This example suspends the NH_EMPLOYEES transfer and then deletes its
 associated schedule.  The error message notifies you that a schedule
 definition cannot be deleted unless the transfer that the definition
 schedules is suspended with the STOP TRANSFER statement.

 SQL> DROP SCHEDULE FOR NH_EMPLOYEES;
 %SQL-F-DDALERR, VAX Data Distributor fatal error
 -DDAL-E-TNSF_NOT_SUSPEN, transfer is not suspended
 SQL> STOP TRANSFER NH_EMPLOYEES;
 SQL> DROP SCHEDULE FOR NH_EMPLOYEES;

 DROP TRANSFER ---> transfer-name ----> ;

Additional information available:

More Informationtransfer-nameExample

 Deletes a transfer definition.  If a transfer has a schedule
 definition, DROP TRANSFER also deletes the corresponding schedule
 definition.

 Specifies the transfer definition to be deleted.

 The following example suspends the NH_EMPLOYEES transfer and then
 deletes its definition.  If a transfer has an associated schedule
 definition, that definition is deleted as well.

 SQL> STOP TRANSFER NH_EMPLOYEES;
 SQL> DROP TRANSFER NH_EMPLOYEES;

 REINITIALIZE TRANSFER -----> transfer-name -----> ;

 Reinitializes a replication transfer to make the source and
 replication databases consistent with each other.  You must
 reinitialize a transfer when someone restores a previous version of
 the source database.

Additional information available:

More Informationtransfer-nameExample

 If you want to reinitialize a particular transfer, the transfer
 definition must be associated with your UIC.

 You can reinitialize a transfer only when the transfer is in the
 suspended state.  To suspend a transfer, first issue a STOP TRANSFER
 statement.  You must execute the REINITIALIZE TRANSFER statement
 outside the scope of a transaction.  If you issue this statement when
 a transaction is outstanding, Data Distributor returns an error
 message.

 After you enter the REINITIALIZE statement, the transfer remains in
 the suspended state.  You must then issue a START TRANSFER statement
 to restart the transfer.

 The REINITIALIZE statement forces the next execution of a replication
 transfer to create a new replication database in the target
 directory.  You must reinitialize a transfer when someone restores a
 previous version of the source database.

 Specifies the replication transfer that you want to reinitialize.

 This example places the LLAMA_REGISTRY transfer in a suspended state
 and then reinitializes it.  The schedule and definition for this
 replication transfer remain in place.  Once the transfer has been
 reinitialized, you can restart it.

 SQL> STOP TRANSFER LLAMA_REGISTRY
 SQL> REINITIALIZE TRANSFER LLAMA_REGISTRY
 SQL> START TRANSFER LLAMA_REGISTRY

 SHOW TRANSFER -+----------------------------+-> ;
                +-+----------------------+-+ |
                  +-> transfer-attribute + | |
    +-------------------<------------------+ |
    +-+--> * --------------+-+---------------+
      ++-> transfer-name --+ |
       +------- , <----------+

 transfer-attribute =

 --> ( -+-+----------------+-+--> ) --->
        | +-> DEFINITION --+ |
        | +-> SCHEDULE ----+ |
        | +-> STATUS ------+ |
        +-------- , ---------+

Additional information available:

More Informationtransfer-attributewildcardtransfer-name
Examples

 Displays information about the transfer definition, schedule
 definition, the transfer status, or all of these transfer attributes.
 When you enter the SHOW TRANSFER statement, you can display
 information about one transfer or all of them, but not about a
 selected number of transfers.

 You must have the Rdb/VMS READ privilege for a database to use the
 SHOW TRANSFER statement.

 The type of information you want displayed about the selected
 transfer or all transfers.  Separate transfer attributes with a comma
 and enclose them in parentheses.

Additional information available:

DEFINITIONSCHEDULESTATUS

 Displays transfer definition information for one transfer, all
 transfers, or a set of transfers you select.

 Displays schedule definition information for one transfer, all
 transfers, or a set of transfers you select.

 Displays the following status information for one transfer, all
 transfers, or a set of transfers you select:

  o  Time the transfer entered its current transfer state

  o  Last transfer status

  o  Time the last successful transfer completed

  o  Next scheduled transfer time (for transfers in the scheduled or
     waiting-to-retry state)

  o  Number of the currently executing retry (for transfers in the
     retrying state)

  o  Number of the next retry (for transfers in the waiting-to-retry
     state)

 The wildcard character (*) displays information about all transfers
 associated with your UIC.  For transfers belonging to other UICs,
 Data Distributor displays the transfer name and the name of the
 transfer definer.  To display information about transfers belonging
 to other UICs, you must have VMS BYPASS or READALL privilege.  If you
 omit the transfer attribute and type SHOW TRANSFER *, Data
 Distributor displays definition, schedule, and status information for
 all transfers.

 Specifies one or more transfers about which you want Data Distributor
 to display information.

 Example 1:  Displaying a schedule definition

 This example displays information about the schedule for the
 NH_EMPLOYEES transfer.  The transfer is scheduled to begin at 1:15
 pm.  to repeat every day.  If the transfer fails, the transfer will
 retry three times with an hour between retry attempts.

 Schedule for transfer NH_EMPLOYEES:
 Start                   22-FEB-1989 13:15:00.00
 Frequency               Every day at 14:30:00.00
 Number of retries       3 times
 Retry frequency         0 01:00:00.00

 Example 2:  Checking on the status of the NH_EMPLOYEES transfer

 This example displays information about the status of the
 NH_EMPLOYEES transfer.  The transfer is scheduled to be performed at
 2:30 pm.  on February 23, 1989.  The transfer ran successfully the
 day before.

 Schedule for transfer NH_EMPLOYEES:
 Start                   22-FEB-1989 13:15:00.00
 Frequency               Every day at 14:30:00.00
 Number of retries       3 times
 Retry frequency         0 01:00:00.00

 START TRANSFER ----> transfer-name ---+
   +-----------------------------------+
   +-+--------------------------+---> ;
     +--> NOW --+->-----------+-+
                +-> WAIT -----+
                +-> NO WAIT --+

 Executes a transfer on demand, or changes the state of a transfer
 from suspended to scheduled, unscheduled, or active.

Additional information available:

More InformationExamples

 You can use the START TRANSFER statement without any qualifiers to
 change the state of a suspended transfer.  Issuing the START TRANSFER
 statement places the transfer in the scheduled state if a schedule
 definition exists for the transfer.  Execution then occurs at the
 next scheduled time.  If a schedule definition does not exist, the
 transfer is placed in the unscheduled state and will execute only
 when you issue a START TRANSFER statement using the NOW qualifier or
 you define a schedule for the transfer.

 You cannot enter the START TRANSFER statement when a transaction is
 outstanding.  You must terminate any outstanding transactions before
 issuing the START TRANSFER statement.

 You can use the START TRANSFER statement to initiate a transfer on
 demand by including the NOW option.  The NOW option immediately
 places the transfer in the active state.  This execute-on-demand
 feature is useful in batch processing environments when you want to
 initiate the transfer after another job has completed successfully,
 regardless of the transfer's schedule.

 If you want to start a transfer, the transfer definition must be
 associated with your UIC.

 Example 1

 This example starts a transfer called ENROLL_SPANISH1.  If this
 transfer has a schedule defined for execution one hour from now but
 the transfer is suspended, issuing the START TRANSFER statement only
 changes the transfer's state to scheduled.  Execution of the transfer
 will not occur for another hour.

 SQL> START TRANSFER ENROLL_SPANISH1

 Example 2

 In this example, transfer ENROLL_SPANISH1 has been defined but has no
 schedule.  You issue this START TRANSFER NOW statement because you
 want to execute the transfer immediately.  Control returns to RDO as
 soon as the transfer begins.

 SQL> START TRANSFER ENROLL_SPANISH1 NOW

 STOP TRANSFER -----> transfer-name -----> ;

 Places a transfer in the suspended state.  Data Distributor does not
 attempt to execute the transfer until you remove it from the
 suspended state using the START TRANSFER statement.  If the transfer
 is in the active state, the STOP TRANSFER statement also stops the
 copy process associated with that transfer.

Additional information available:

transfer-nameExample

 Specifies the transfer to be suspended.
3$More_Information

 You must terminate any outstanding transactions before you issue a
 STOP TRANSFER statement.

 If you want to stop a particular transfer, the transfer definition
 must be associated with your UIC.

 The following example places the EUROPE_PERS transfer in the
 suspended state.

 SQL> STOP TRANSFER EUROPE_PERS

 data-type =
  -+-> CHAR -+--------+---------------------------+-->
   |         +-> (n) -+                           |
   +-> VARCHAR (n) -------------------------------+
   +-> LONG VARCHAR ------------------------------+
   +-> TINYINT --------------+-----+--------+-----+
   +-> SMALLINT -------------+     +-> (n) -+     |
   +-> INTEGER --------------+                    |
   +-> BIGINT ---------------+                    |
   +-> QUADWORD -------------+                    |
   +-> LIST OF BYTE VARYING -+                    |
   +-> DECIMAL -+-+-----------------------------+-+
   +-> NUMERIC -+ +-> ( --> n -+--------+-> ) --+ |
   |                           +-> , n -+         |
   +-> FLOAT -+--------+--------------------------+
   |          +-> (n) -+                          |
   +-> REAL --------------------------------------+
   +-> DOUBLE PRECISION --------------------------+
   +-> date-time-data-types ----------------------+

Additional information available:

More Informationdate time data typesdomains

 Data types control how SQL interprets and stores values in columns.
 Literals, arithmetic expressions, parameters, and SQL functions are
 examples of expressions other than column names that supply values
 and also have associated data types.

 date-time-data-types =
 --+-> DATE -+----------+-----------------+-->
   |         +-> ANSI  -+                 |
   |         +-> VMS ---+                 |
   +-> TIME ---> frac --------------------+
   +-> TIMESTAMP --> frac ----------------+
   +-> INTERVAL ---> interval-qualifier --+

Additional information available:

fracinterval qualifier

 frac =
 --+-----------------------------------+->
   +--> ( ---> numeric-literal --> ) --+
 Specifies the time or timestamp precision to a fraction of a second

 interval-qualifier=

 --+-> YEAR ---> prec --+-------------+-----------------+->
   |                    +-> TO MONTH -+                 |
   +-> MONTH --> prec ----------------------------------+
   |                                                    |
   +-> DAY ----> prec --+-------------------------------+
   |                    +-> TO -+-> HOUR ---------------+
   |                            +-> MINUTE -------------+
   |                            +-> SECOND -> frac -----+
   +-> HOUR ---> prec --+-------------------------------+
   |                    +-> TO -+-> MINUTE -------------+
   |                            +-> SECOND -> frac -----+
   |                                                    |
   +-> MINUTE -> prec --+-------------------------------+
   |                    +-> TO SECOND ------> frac -----+
   |                                                    |
   +-> SECOND -> seconds-prec --------------------------+

Additional information available:

precseconds prec

 prec =
 --+-----------------------------------+->
   +--> ( ---> numeric-literal --> ) --+
 Specifies the interval leading field precision, which restricts the
 number of decimal digits that the leading segment occupies.

 seconds-prec =
 --+--------------------------------------+-->
   +-> ( -> numeric-literal-1 --+         |
      +-------------------------+         |
      ++--------------------------+-> ) --+
       +> . -> numeric-literal-2 -+
 The first numeric literal specifies the interval leading field
 precision for the interval, and the second specifies its fractional
 seconds precision.

 A domain is the set of values that a column in a table can have.  The
 CREATE DOMAIN statement specifies the set of values by associating a
 data type with a domain name.

 You can refer to a domain instead of an SQL data type in the CREATE
 and ALTER TABLE statements, and in formal parameter declarations in
 SQL module procedures.  You can specify the same domain in many table
 definitions.  If the domain has to change, you need only change that
 one domain definition to change all the tables and SQL modules that
 refer to it.  This ability makes it easier to keep applications
 consistent.

 Gives access to DCL from inside interactive SQL.

 The dollar sign ($) instructs interactive SQL to spawn a subprocess
 and pass the rest of the command line to DCL for processing.  You
 must follow the dollar sign with a DCL command.  After DCL processes
 the command, it logs out of the subprocess and returns control to
 interactive SQL.  For example:

 SQL> $ MAIL

 MAIL>

Additional information available:

Example

 Seeing your current default VMS directory:

 SQL> $ DIRECTORY

 Directory DISK2:[DEPT3.ACCT]

 DEFPRO.SQL;6    NOTEQUAL.SQL;1   QUERY.SQL;1    REFEXAM.SQL;12
 STORE.SQL;1     UPDATE.SQL;2

 Total of 6 files.

 SQL>

 SQL allows you to specify an alias that declares the database as the
 default database.  Specifying a default database means that
 subsequent statements during the database attachment that refer to
 the default database need not use an alias.

 In the SQL module language, the alias specified in the module header
 is the one that designates the default database.  In precompiled SQL
 programs and in interactive SQL, the special alias RDB$DBHANDLE
 designates the default database.  In all environments, omitting an
 explicit alias is the same as specifying the alias that designates
 the default database.

 Select More_Information to continue.

Additional information available:

More Information

 If you do not declare any alias or attach to any database, SQL
 declares the database specified in the logical name SQL$DATABASE as
 the default database, using the FOR FILENAME clause.

 If you declare a database specifying an alias other than the one that
 declares the default database, you must use that alias to qualify
 names of any database elements to which you refer in SQL statements.
 If you omit the alias, SQL assumes the table or view must be part of
 the default database.  If there is no default database and you omit
 the alias, SQL generates an error.

 Dynamic SQL lets programs accept or generate SQL statements at run
 time, in contrast to SQL statements that are part of the source code
 for precompiled programs or SQL module language procedures.  Unlike
 precompiled SQL or SQL module language statements, such dynamically
 executed SQL statements are not necessarily part of a program's
 source code, but can be created while the program is running.
 Dynamic SQL is useful when you cannot predict the type of SQL
 statement your program will need to process.

 You cannot use dynamic SQL statements in interactive SQL, but
 interactive help includes quick reference information on these
 dynamic SQL statements:

 Dynamic DECLARE CURSOR (listed as Dyn_DECLARE_CURSOR)
 DESCRIBE
 EXECUTE
 EXECUTE IMMEDIATE (listed as EXECUTE_IMMEDIATE)
 Extended Dynamic DECLARE CURSOR (listed as Ext_Dyn_DEC_CURSOR)
 Dynamic FETCH (listed as Dyn_FETCH)
 INCLUDE
 Dynamic INSERT (listed as Dyn_INSERT)
 Dynamic OPEN (listed as Dyn_OPEN)
 PREPARE

 Declares a cursor where the select statement is supplied at run time
 in a parameter.

Additional information available:

Format

 DECLARE cursor-name ----------------------+
 +-----------------------------------------+
 +-+----------------+----> TABLE CURSOR ---+
 | +-> INSERT ONLY -+                      |
 | +-> READ ONLY ---+                      |
 | +-> UPDATE ONLY -+                      |
 | +---------------------------------------+
 | +-> FOR -> statement-name --------------+
 | +---------------------------------------+
 | ++------------------------------------+-+
 |  +> OPTIMIZE FOR -+-> FAST FIRST --+--+ |
 |                   +-> TOTAL TIME --+    |
 | +---------------------------------------+
 | +-> FOR -> statement-name --------------+> ;
 |                                         |
 ++----------------+> LIST CURSOR ------+  |
  +-> INSERT ONLY -+                    |  |
  +-> READ ONLY ---+                    |  |
  +-------------------------------------+  |
  +-> FOR -> statement-name ---------------+

Additional information available:

INSERT_ONLYREAD_ONLYTABLELIST

statement name

 Insert-only cursors position themselves on a row that has just been
 inserted so that you can load data values into lists or rows of that
 row.

 Read-only cursors can be used to access row information from a result
 table whenever you do not intend to update the database.  For
 example, you could use a read-only cursor to fetch row and column
 information for display.

 Specifies a cursor used to access individual rows of result tables.
 If you do not specify a cursor type, SQL declares a table cursor by
 default.

 Specifies a cursor used to access lists.

 A list is an ordered collection of elements of the data type LIST OF
 VARBYTE (also called LIST OF BYTE VARYING).  A list is equivalent to
 an RDO segmented string.  You can use lists to scan through very
 large data structures from within a language that does not support
 objects of such size.

 Lists exist as a set of elements within a row of a table.  Each list
 cursor must reference a table cursor, which provides the row context.

 Identifies a prepared select statement that is generated at run time.

 The dynamic FETCH statement positions a list cursor onto the next
 element within a list.  The dynamic FETCH statement is a FETCH
 statement that references a dynamic list cursor.

 You cannot use a dynamic FETCH statement before you issue a dynamic
 OPEN statement for the specified list cursor.

 If the list element is longer than the target specification, SQL sets
 the sixth element of the SQLERRD array of the SQLCA to the difference
 between these two values (the number of truncated bytes).

Additional information available:

Format

 FETCH ---> dynamic-list-cursor-name --------------+
                                                   |
         +-----------------------------------------+
         |
         +--> USING DESCRIPTOR descriptor-name ---->;

 Inserts new data into a dynamic cursor (positioned insert) or a list,
 depending on which syntax you use.  For more information, see the
 Positioned and LIST subtopics.

Additional information available:

LIST

Positioned

 Use the following syntax when you want to insert data into a dynamic
 table cursor to set up the proper row context for any list cursors.
 This type of INSERT statement is known as a dynamic positioned insert
 statement.
 INSERT INTO CURSOR ---> dynamic-cursor-name --------+
                                                     |
   +-------------------------------------------------+
   |
   +-+----------------------------+------------------+
     +-> ( -+ column-name -+-> ) -+                  |
            +------ , <----+                         |
   +-------------------------------------------------+
   +-> VALUES --> ( -++-> literal ---++--> ) ------------>;
                     |+-> parameter -+|
                     |+-> NULL ------+|
                     |+-> USER ------+|
                     +---- , <--------+

 Inserts new data into a list.

 INSERT INTO CURSOR ---> dynamic-cursor-name ---+
                                                |
   +--------------------------------------------+
   +--> VALUES --> ( -++-> literal ---++-> ) --> ;
                      |+-> parameter -+|
                      +----- , <-------+

 Opens a dynamic list cursor so that you can retrieve its elements
 through dynamic FETCH statements.

Additional information available:

Format

 OPEN ---> dynamic-list-cursor-name -------------->;

 The following topics document messages returned with the SQL facility
 code.  The online file SYS$HELP:SQL$MSG.DOC contains the same text.
 Print that file if you need hardcopy SQL message documentation.

 The Appendix on error messages in the VAX SQL Reference Manual
 describes how to use this file and files documenting related error
 messages with other facility codes.

Additional information available:

2DBTRISTMTACENOTFNDACE_ID_OVFLACE_ID_UNFL
ADADISUNSADAVARUNSAGGTBLCURALIASEMBFIRST
ALIASONLYONCEALLSCHROLLALLSCHTABALTNOTOCB
ALTSCHATTAMBHV_DECAMBTYP_DECAMB_KEYWORD
ANODBHANDANSIPROTONLANSI_UPDATE_VIEWARGCOUNT
ARIEXPEXPASSSTRLITATTMISSINGBACKUPBYBADADJLOCKGRAN
BADARGAVGBADARGSUMBADBLOBBADBUFFERPOOL
BADCATALOGBADCATINCREBADCBDATEBADCLUMP
BADCOLIGNCASBADCOLLATIONBADCORATTBADCTXLEN
BADCTXTYPEBADCTXVERBADDBHANDBADDBKEY
BADDICTIONARYBADDTFMTBADEPILOGUEBADEPINAM
BADEXTENDIBLEBADFILEVERBADFLDTYPBADIDXMAP
BADINTERVALBADLANGUAGEBADLOGFILEBADLOGNAM
BADMAINTBADMETNAMBADMVIEWFLDBADMVIEWREL
BADMVIEWVEWBADMVRELSBADMVVIEWSBADNONEXTEND
BADORIENTBADPAGEFORMATBADPREPAREBADPROLOGUE
BADPRONAMBADPROTECTIONBADRECBUFBADROLMVFLD
BADSCHEMABADSCHINCREBADSEGSTRINGBADSNAPFILENAME
BADSTOGROUPBADSUPLVLBADTHRESHOLDBADVAXCLUSNODES
BADVERNUMBAD_ARRAYBAD_CDD_DEFBAD_DB
BAD_LENGTHBAD_LEVELBAD_NAMEBAD_PRECISION
BAD_SCALEBAD_TOKENBAD_TXN_STATEBAD_VERSION
BASROWDELBINSCAFACBIT_FIELDBOG_DYN_NAMEBOOEXPEXP
BUGCHKCABORTCANTDOVALXPRCANT_MOVECATNOTDEF
CAT_EXISTSCDDERRCDDUNKPROTCDDVERERR
CHAR_SET_USEDCHECKOPTROCHGINDMAPCHGINDMAPSTP
CHRUNIBADCHR_TOO_SHOCHR_TOO_SMACIRCTYPE
CLOSERRCMDINTRCMPBYINVWCMPBYMVMETOOCMPBYWNRL
CMPBYWNVWCNTSPNSUBCOLEXISTSCOLLSTINVCOLL_EXISTS
COLNOTFUNCOLNOTNULCOLNOTSSCOLNOTUPD
COLNOTVALCOLONDISILLCOLONENAREQCOLSEQNOTDEF
COMPNOTRANSCOMPONENTCOMTOOLONCONALREXI
CONCHAILLCONDICREQCONLYOPTCONNAMEXI
CONNOTDEFCONNOTSUPCONREAATTCONSNAATT
CONTPREQCONTPROMPTCONTRIACTCONVARDEF
CONVARILLUPDCONVARUNDCORREFFUNCREATEDATE
CRE_STO_ERR_SCHCSETNOASCIICSETSYNCS_ERRCTXIGNORED
CTXPARMNOTALLCURALRDCLCURALROPECURNAMEXI
CURNOTOPECUROFNOTCUROFREQCUROFSTACURSTMTTXN
CURTWOOPENCURUSEINVCURVERDATCONERR
DATEADDILLDATEDIGNEQDATEDIVILLDATEEQLILL
DATEFORTIMESDATEMULILLDATEOPRDATESCANEQ
DATESUBILLDATETIMESDATETIME_PRECDATETIM_PREC
DATETIM_SCALEDATETYPESDATIM_SCALEDATNOTSUP
DATTYPUNKDBALLOCISDBALLOCWASDBBUFLENIS
DBBUFLENWASDBCLWASOFFDBCLWASONDBENVSYNERR
DBFCINTVLISDBFCINTVLWASDBFCISOFFDBFCISONDBFCWASON
DBHANDOVEDBHANDOVE_QDBHANDUNKDBHDLREQ
DBINUSEDBJNLALLISDBJNLALLWASDBJNLEXTIS
DBJNLEXTWASDBJRNCMTISNDBJRNCMTISYDBJRNCMTWASN
DBJRNCMTWASYDBKAMBIGDBKTOOBIGDBLCKTMOUTIS
DBLCKTMOUTWASDBMUNGEDDBMUNGED_QDBNAMCONF
DBNOTINCONNDBNUMBUFISDBNUMBUFWASDBNUMDBRIS
DBNUMDBRWASDBNUMNODISDBNUMNODWASDBNUMUSERIS
DBNUMUSERWASDBPGSIZISDBPGSIZWASDBSNPDEFISN
DBSNPDEFISYDBSNPDEFWASNDBSNPDEFWASYDBSNPENAISN
DBSNPENAISYDBSNPENAWASNDBSNPENAWASYDBSPECSYNERR
DB_EXISTSDB_HANDECDB_HANDEC2DB_HANLON
DB_IN_TXNDCLBEFEXEDCLDATBEFDDALERR
DDALFMTUNKDDALNOTINSDDLPARAMDDNOTSUPP
DECCURINTODECEMBERDEFCONMODDEFDBDECDEFVALINC
DEFVALNOTCBDEFVALUNSDEGMODSPCDELBACKUP
DELLSTDYNCURDEPIMPCASDEPR_DQUOTESDEPR_FEATURE
DEP_FEATUREDIC_DB_CHG1DIC_DB_CHG2DIFFDEFINV
DIFFSCHVIEWDIGNUMPICDOMNOTBCKDOM_CDD_NAME
DOM_INVALIDDPBFMTUNKDROP_COLDOMDROP_COLL
DROP_CONSDROP_DOMDROP_IDXDROP_STOMAP
DROP_STORMAPDROP_TABLEDROP_TRIGDROP_VIEW
DTFMTTOOBIGDTONCEEACHDUPFLDDEFDUPPROCNAM
DUPREFACTDUPVARDYNSIZARREMPMSGVEC
ENDENUM_VARERRATTDECERRATTDEF
ERRCRESCHERRDETERRINCPATHERRSYMDEL
ERRSYMREPES_ILL_RPTEVACLAUNSEXESELSTA
EXPNUMLITEXPQUEXPREXP_CDD_NODATAEXP_CDD_NOEXT
EXP_CONVERTEXTNAMEXISTSEXTRADATAEXTREPONESCH
FETNOTDONFIELD_EXISTSFINNOSESFKCONSNOTCB
FLDAMBIGFLDNOTBCKFLDNOTCRSFLDNOTDEF
FLDNOTINRELFLUINPBUFFORCOLNMASSFORCOLNMDECL
FORCOLNODECLFORPASLENFORTABNODECLFUN_VAR
GARBLEDGETCRESEGGFLOATHEXSTREVEHI_ORD_LOS
HVNOTDECLHV_NOT_INIDMISSINGIGNCASE_BAD
ILLBEGINILLCHARILLCOMPRECILLDATLENILLEXEIMMILLFLOLEN
ILLFRASECPREILLFROMILLHEXNUMILLINTLENILLPICSTR
ILLSTRCONTIMPL_DIMIMP_CDD_NODATAIMP_IDXNOTCRE
IMP_IDXNOTDROIMP_IDX_CONFLICTIMP_IDX_DELIMP_IDX_NODEL
IMP_IDX_OVRIMP_IDX_TWICEIMP_MAP_DELIMP_MAP_OVR
IMP_STANOTDROIMP_STAREADONLYIMP_STMNOTCREIMP_STMNOTDRO
IMP_STO_AREAIMP_STO_CONFLICTIMP_STO_DELIMP_STO_MAP_CONFLICT
IMP_STO_MAP_TWICEIMP_STO_OVRIMP_STO_TWICE
IMP_TRA_BEGIMP_TRA_ENDINCCSASSINCCSCMPINCCSCON
INCNOTRECINC_DAT_TYPINDEXTSINDFIXINTINDNOTDEF
INDSHOINTIND_EXISTSINFODETINPUTERRORINSCOLALR
INSCURDYNINSVALSPECINS_INTO_ROINS_MUST_INS
INTERVAL_USEDINTIGNSYSINTNOTQUALINTNOTSYSINTONOTALW
INTONOTQUALINTQUALINVINTVALLOWINTVALOVR
INT_DEL_FLD_PATHINT_DEL_REL_PATHINVACLINVARRSUB
INVATTVALINVCHAINPINVCHANUMSTRINVCOLLSTINVCOLSPCINVCOMLIN
INVCONSINVCORRSLINVCSETINVDATCONINVDBKREF
INVDISXPRINVESCVALINVFLDINVFUNREFINVHVDECL
INVINDEXINVINTQUALINVLENHVINVNODESIZEINVNUMLIT
INVNUMSTRPREINVOBJFILINVORDNUMINVPERCENTFILL
INVPICNINVPRIVINVPRIVNAMESINVQUALINVREFCLA
INVRELVIEWINVRNGINVRTOSTMINVSEGVALINVSELLIS
INVSELSTARINVSQLCODEINVSSCONVINVSSHAN
INVSTRLENINVTRGINVTRISTMTINVTYPEINVVALLISIOERROR
ISQLINTOJOITOOBIGJUNONLINKEYTOIDENTLANFILEXTLANSWIVAL
LANUNSDSCDTPLANUNSDTPLCKTMOUTISLENMISMAT
LIMFIXINTLINETOOLONGLISTNOTVALLIT_EXCEPT
LOGBACDATLOOK_FORLOOK_FOR_CONLOOK_FOR_FIN
LOOK_FOR_STMTLOOK_FOR_STTLOOK_FOR_UNTERMLOWCASNOTALL
LOW_ORD_LOSLSTCURSTALSTNOTNULLSTREFAMB
L_PAGE_HEAD_2MAJORVERMAXFLDPRTSTRMAXNESEXC
MAXORDEXCMAXRELEXCMINGTRMAXMINORVER
MINUSDATINTMISREQVALMISSINGNAMEMIXTABLIS
MLTDFNRTNMODTOOOLDMOVENOCOLSMULDIMARR
MULSPECATRMULTSPECATRMULT_STRUCTMUL_UIC
MVMULTITARGMVRELABSNTNAMCONFNAMTOOBIG
NEG_DIMNESFUNINVNESINCFILNESQRYEXPNO1ST
NOAGGALLNOALTERNOANYALLNOBATCHUPDATENOBATUPDNOBCKFIL
NOBCKTRNSNOBUCTXPARMNOBUUSINGCTXNOCATRES
NOCDDNOCDDALTNOCDDRESNOCDDUPDATNOCMPBYRES
NOCMPINTDYNOCOLALLNOCOLLSTNOCOLNAMNOCOLRES
NOCONNAMNOCONRESNOCORRCOLNOCPRIRES
NOCSETNOCUROFNODATDIVNODATRESNODBHALWNODBKALL
NODBKGRONODBNAMENODBSINTXNNODECLMOD
NODEFDBNODISTINCTNODROPSYSCATNODROPSYSSCH
NODUPLIVIEWNOENTRYPTNOFILLISTNOFLDRESNOFSTINREPT
NOGROUPNOIDXRESNOIMPTXNNOINCDICNOITEMDEFNOLANGFIL
NOMAPIMPONOMAPRESNOMATCHKEYNOMLTIMVNOMLTIMVIEW
NOMODFILNOMOVESYSNOMVRALLNOMVVROLNONCONARR
NONOVALNONSINGLE_INTONONSTAAMBNONSTAANSPARM
NONSTACASNONSTACOBNONSTACOLNONSTACOLQUAL
NONSTACONNONSTACUCNONSTACURNONSTADIS
NONSTADTPNONSTADYNNONSTAHVNONSTAINVOKER
NONSTANAMNONSTAOKWNONSTAPHYNONSTAQUO
NONSTARSWNONSTASCLNONSTASMNONSTASYN
NONSTATXNNONSTAUNINONSTAVIANOOPENCUR
NOORDERNOPASQLDANOPHYSMULSCHNOPRECOMPSEL
NOPRIMKEYNOPROCNOPRVMVIEWNOPRVMVREL
NOPRVREPLINOPRVROLMVRNORDBPRIVNOREDINREPT
NORELFOUNORELRESNOREMVERNOREPSQLDANORETURN
NOROCOLNORTPARMNOSCHALTNOSCHRESNOSEGSTRAREANOSELALL
NOSELXPRNOSORTINREPTNOSPRIRESNOSQLCANOSQLCODE
NOSTRDEFNOSTRNAMNOSUCHCONNOSUCHCURNOSUCHDATEFMT
NOSUCHLANGNOSUCHPROCNOSUCHSTMTNOSUCHTIMEFMT
NOSUPREPLINOTAVIEWNOTDB2NOTDB2DURNOTDB2FN
NOTFOUNDNOTGROFLDNOTHVDECLNOTIMPSES
NOTINSCURNOTINTBLCURNOTLISTCOLNOTLSTCUR
NOTPRIRESNOTRGRESNOTSAMESCOPENOTSAMETBL
NOTTBLCURNOTUSEINDNOTYPESNOT_A_DB
NOT_CDD_DBNOT_SAME_CONTEXTNOT_SCH_IDNOUNION
NOVIERESNOVIEWINREPTNOWHERENO_CDDACCNO_COMMAND
NO_DCLTXNNO_DECIMALNO_DESCENDINGNO_DMLPLAN
NO_ENDCOMNO_ENDEXECNO_FILFNDNO_HDRPLAN
NO_INCFNDNO_NUMERICNO_PLNFNDNO_SQLDA
NO_STMTB4HDRNO_SUCH_FIELDNO_TRIGGER_VALSNO_TXNOUT
NO_UNSNUMERICNSEGBLRNULLNOINDNUMCMPTXT
NUMHVSNOTNUMITESELNUMXPREXPNUM_TO_DATE
OLDNAMWASONEEPERMONETXNMODONLFIRPRE
ONLFIRVARONLONEDBONLONETRNONLVALLSTONLY1LISTONLY1TBL
ONLYONEPSECTOPENERROPRSTK_OVRFLOPARAMNOTSTR
PARAMQUALPARBADCLAPARBADDATPARBADLEN
PARBADSCAPARBINSCAPARMLISTREQPARSE_STACK_OVERFLOW
PASPRGNOTFNDPASRECUNSPASVARUNSPATH_NAM_REQ
PHYBACDATPKCONSNOTCBPKGNAMCHGPKNOTNULL
PREFORSTRPREMATURE_EOFPREPCDDVER1PREPCDDVER2
PREPCDDVER3PREPDBVERPREPNOCTXSTRPREPPROMPT
PRESTAOPEPRIKEYEXIPRINT_SSIDPROCNOCAPROCSTATWO
PROMPTPRPSELINTOPRVERRSDTPUNKPTR_VARPUTOPESEG
QUAINVVALQUALNOTALLOWQUANOVALQUERYCANQUERYLIMPOS
RDBVMSONLREANOWRTREAONLATTRECEXCMAX
REFKEYCOLREFKEYNUMRELNOTDEFREL_EXISTS
REMNOTALWREORGONLALTSMRESABORTRESERVED_WORD
RESRELMSGRESVIEMSGRESWORDCHKOFFRESWORDCHKON
RES_KEYWORDRES_WORD_AS_IDENTRETRYPOSREVENTANS
RTCSASS_C2CRTCSASS_C2NRTCSASS_D2CRTCSASS_N2C
SATURDAYSCHCATMULTISCHEMA_CDDFILESCHNOABSTIM
SCHNOTDEFSCH_EXISTSSEGAREERRSEGSTRAWAS
SEGSTREXPSELMORVALSESNOTENASEVERRDET
SHCONSHCONNONESHCONRELSHDBCDDSHDBFILSHDBINFIL
SHDBPTHSHDESCENDSHEXECOFFSHEXECONSHFLDGBL
SHFLDNONESHFLDRELSHFLDVIEWSHINDDRSHINDDUP
SHINDFSHINDFLDSIZESHINDIFSHINDMAPVALSHINDMAPVAL2
SHINDNDUPSHINDNONESHINDRSHODEPROFF
SHODEPRONSHOFLAGOFFSHOFLAGONSHOTABMAPDR
SHRELNONESHTYPNONESHVIEWSHVIEWNONE
SMA_DAT_TYPSPACREQSPANOTVALSQL41UNAS1
SQL41UNAS2SQL41UNAS3SQL41UNAS4SQL41UNAS5
SQLCHSCALESQLDANOTSQLDATASQLLENSQLTYPESSTOOBIG
STANOTDEFSTANOTSELSTAREQCOLSTARNOTALL
STAROCURSTATWOCURSTMTALREXISTOCOLERR
STOCOLUKNSTOMAPNOTDEFSTOMAP_EXISTSSTOTABUKN
STRARRAYSTRCVTNUMSTRINXPRSTRLITEXPSTRLITMISQUO
STRMORELESTRTOOBIGSTRTOOLONSTRXPREXP
SUBNOGBSUBTOOVALSYMDEFSYM_EXPSYNTAX_ERR
SYSPAGFORSYSPAGUNIS_ALGDISS_ALGENABLEDS_ALLINDDBF
S_ALLINDDBHS_ALLINDDBPS_ALLTBLDBFS_ALLTBLDBH
S_ALLTBLDBPS_ALLTYPDBFS_ALLTYPDBHS_ALLTYPDBP
S_BATCH_UPDATES_BLANKSS_COLHDR1S_COLHDR2
S_COMMENTS_COMMIT_CONSTS_COMPUTEDS_COMTBL
S_CONCOMMITS_CONCURRENCYS_CONNODEFERS_CONSISTENCY
S_CONSSGLLEVS_CONVERBS_DBCDDPATHS_DBHAN
S_DB_LCKTIM_INTVLS_DEFDBS_DESCRIPTIONS_DICTS_FC_COM
S_FC_INTS_FC_NOCOMS_FC_TIMS_FC_TSNS_FLDADTS_FLDB_NS
S_FLDB_SS_FLDFS_FLDGS_FLDL_NSS_FLDL_SS_FLDNL
S_FLDNUS_FLDPS_FLDQ_NSS_FLDQ_SS_FLDSSS_FLDSS_BLR
S_FLDSS_SEGLENS_FLDSS_TXTS_FLDSS_TYPS_FLDT
S_FLDUNKS_FLDVTS_FLDW_NSS_FLDW_SS_GB_DISABLE
S_GB_ENABLEDS_INSERT_COUNTS_INTEGNPRESS_INTEGPRES
S_LINES_LIST_STOMAP_NAMES_LOCK_ERS_LOCK_EW
S_LOCK_PRS_LOCK_PWS_LOCK_SRS_LOCK_SW
S_LONG_BLANKSS_LONG_DESCRIPTIONS_MULTLEV
S_NOWAITS_PRIV_DBS_PRIV_TBLS_PROT_DB
S_PROT_TBLS_QUERY_HEADERS_RDBVMSFILS_READONLY
S_READ_WRITES_SERDBSEVMSFILS_SNGLEVS_SOURCES_STOAREA_READONLY
S_STOAREA_READWRITES_STOAREA_UNIFORMS_STOAREA_WRITEONCE
S_STOMAP_NAMES_SYSINDDBFS_SYSINDDBHS_SYSINDDBP
S_SYSTBLDBFS_SYSTBLDBHS_SYSTBLDBPS_SYSTYPDBF
S_SYSTYPDBHS_SYSTYPDBPS_TBLINFO1S_TBLINFO2
S_TRANSBRIEFS_TRANSFCOMMENTS_TRANSFDEFS_TRANSFDEFINER
S_TRANSFDEFNONES_TRANSFDELTAS_TRANSFDESTDBS_TRANSFEPILOG
S_TRANSFERSS_TRANSFINF1S_TRANSFINF2S_TRANSFLAST
S_TRANSFLINES_TRANSFLOGFILES_TRANSFMODEES_TRANSFMODEER
S_TRANSFMODERS_TRANSFNEXTS_TRANSFNOEPIS_TRANSFNOLOG
S_TRANSFNONES_TRANSFNOPRIVS_TRANSFNOPROS_TRANSFNOSTS
S_TRANSFPROLOGS_TRANSFRETRIEDS_TRANSFRETRYS_TRANSFSCH
S_TRANSFSCHDAYS_TRANSFSCHDLTS_TRANSFSCHDPWS_TRANSFSCHDPW2
S_TRANSFSCHMONS_TRANSFSCHNONES_TRANSFSCHONCS_TRANSFSCHWEK
S_TRANSFSOURCES_TRANSFSRCDBS_TRANSFSRCNOHS_TRANSFSTART
S_TRANSFSTATUSS_TRANSFSTSS_TRANSFSTSACTS_TRANSFSTSNONE
S_TRANSFSTSRETS_TRANSFSTSSCHS_TRANSFSTSSSPS_TRANSFSTSUNS
S_TRANSFSTSWTRS_TRAN_BASESYSS_TRAN_DBHANDLES_TRAN_DECLARE
S_TRAN_DEFDBS_TRAN_HEADERS_TRAN_NOBASSYSS_TRDPB2AIJ
S_TRDPB2AIJALLS_TRDPB2AIJCONTS_TRDPB2AIJEXTS_TRDPB2AIJONCE
S_TRDPB2AIJSPLS_TRDPB2ALGS_TRDPB2ALGDISS_TRDPB2ALGENA
S_TRDPB2ALLOCS_TRDPB2AUTOS_TRDPB2BADCODES_TRDPB2BFLEN
S_TRDPB2CDDMNTS_TRDPB2CDDPATHS_TRDPB2CDDREQS_TRDPB2CHGSTO
S_TRDPB2CONVERTS_TRDPB2DBRBUFFS_TRDPB2DEFSTOS_TRDPB2DELSTO
S_TRDPB2DESCRS_TRDPB2ENDSTOS_TRDPB2EXSGRWS_TRDPB2EXSMAX
S_TRDPB2EXSMINS_TRDPB2EXSPGSS_TRDPB2EXTBLES_TRDPB2EXTGRO
S_TRDPB2EXTMAXS_TRDPB2EXTMINS_TRDPB2EXTPGSS_TRDPB2FILESPC
S_TRDPB2FILETYPS_TRDPB2HEADERS_TRDPB2LAYRACCS_TRDPB2MANUAL
S_TRDPB2NUMBFS_TRDPB2NUMNODES_TRDPB2NUMUSRS_TRDPB2PGSIZE
S_TRDPB2PROTS_TRDPB2READONLS_TRDPB2REQSCOS_TRDPB2SEGAREA
S_TRDPB2SNAPS_TRDPB2SNPALLS_TRDPB2SNPDISS_TRDPB2SNPENA
S_TRDPB2SNPENDS_TRDPB2SNPENIS_TRDPB2SNPFLGS_TRDPB2SPAMINT
S_TRDPB2SPAMSS_TRDPB2SPMTHR1S_TRDPB2SPMTHR2S_TRDPB2SPMTHR3
S_TRDPB2STONAMES_USRINDDBFS_USRINDDBHS_USRINDDBP
S_USRTBLDBFS_USRTBLDBHS_USRTBLDBPS_USRTYPDBF
S_USRTYPDBHS_USRTYPDBPS_VALIDS_VERB_CONST
S_VIDANAMS_WAITS_WAIT_INTERVALTBLCOLAFT
TBLCURDYNTBLNOTCURTBL_CDD_NAMETHRESHIGNO
THRIGNSYSTHRNOTSYSTOKINSBEFTOKTOOBIG
TOOBIGBLRTOOMANYNAMESTOOMANYTBLTRAACT
TRAACT_1TRAACT_2TRAACT_3TRADBPNEWONLTRAHDLINV
TRAMODSPCTRANOTOWNERTRANSFDISTREPTRANSFGRPBY
TRANSFHAVINGTRANSFSUBQRYTRANSFUNIONALLTRATOEXEXTR
TRATOEXPRIVTRATOEXRDBTREE_OVRFLOTRIGNOTDEF
TRIG_EXISTSTRNNOTBLSTRNNOVIEWSTWOIMPTXN
TXNNOTLONGTXN_HNDL_IGNOREDUKN_ALT_OPTUNAOBTDSR
UNBDECFILUNBTMPFILUNDEFVARUNDPARAM
UNDVERUNICONSNOTCBUNIKEYEXIUNIONEXTROLLUNISELLIS
UNKTYPEUNMATENDUNSCOMPBYUNSDATASSUNSDATATYPE
UNSDATCVTUNSDATXPRUNSDB2PRIVUNSDSCCLA
UNSDTPCVTUNSIGNED_VARUNSNUMXPRUNSPLIATT
UNSSTRXPRUNSSUPDATUNSUPOPUNSUPVERUNTSTR
UPDCOLPRIVUPDINSCURUPDREACURUSERINVIEW
USERNOTSUPUSINGCTXNOTALLUSRDEFTYPVECNOTIND
VEWNOTDEFWAIMODSPCWARDETWARNINGCB
WHYTWICEWILDALLWILDWISH_LISTWRICIRREF
YES_CHARZABORTZEROSIZE