Additional information available:

$@ALTERBEGIN_DECLARECLOSECOMMENT_ON
COMMITCREATECURRENT_TIMESTAMPDBKEYDECLARE
DELETEDESCRIBEDROPEDITEND_DECLAREEXECUTE
EXECUTE_IMMEDIATEEXITEXPORTFETCHFINISHGRANT
HELPIMPORTINCLUDEINSERTINTEGRATELSE
NULLOPENPREPAREPRINTQUITRELEASEREVOKE
ROLLBACKSELECTSETSET_ALL_CONSTRAINTSET_TRANSACTION
SHOWSQLCASQLDAUPDATEUSERWHENEVER

aliasarith expressionauthorization idcol select expr
Command recalldatabase handleData Distributordata types
DCL invokedefault schemaDynamic 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

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

 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.  However, SQL does not permit arithmetic operations on
 columns defined with the DATE data type.

 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:

More Information

 The arithmetic operators and their functions are:

 +       Add
 -       Subtract
 *       Multiply
 /       Divide

 Select More_Information to continue.

Additional information available:

More Information

 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 or DECLARE SCHEMA statement, whether
 you specify a file specification or a data dictionary path name, you
 can specify an additional name, called an authorization identifier.
 You must specify an authorization identifier in CREATE SCHEMA but it
 is optional in DECLARE SCHEMA.

 An authorization identifier is a name for a particular attachment to
 a schema.  Explicitly specifying an authorization identifer lets your
 program or interactive SQL statements refer to more than one schema.
 Once specified, you must use the authorization identifier when
 referring to the schema in subsequent SQL statements (unless those
 statements are within a CREATE SCHEMA statement).  You must use an
 authorization identifier when you declare more than one schema.

 DIGITAL proprietary database languages (such as RDO in Rdb/VMS) use
 the term database handle instead of authorization identifier.  The
 two terms mean the same thing.  The keywords AUTHORIZATION ID in SQL
 and DB_HANDLE in RDO are also synonymous.

 col-select expr =

 ---+-+-> col-select-clause  ---+--->
    | +-> ( col-select-expr ) --+
    | +------------<------------+
    | +-> UNION ---+-------+----+
    |              +->ALL -+    |
    +----------<----------------+

Additional information available:

UNION

col select clauseMore Information

 col-select-clause =

 SELECT -+------>------+-+-> * --------------------+-+
         +-> ALL ------+ +-> table-name --+-> .* --+ |
         +-> DISTINCT -+ +-> view-name ---+        | |
                         +-> alias -------+        | |
                         +-> value-expr -----------+ |
   +--------------------------------<----------------+
   + FROM -++-> table-name -+-+----->----+-+-+--------->----------+-+
           |+-> view-name --+ +-> alias -+ | +-> 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.

 DIGITAL proprietary database languages (such as RDO in Rdb/VMS) use
 the term database handle instead of authorization identifier.  The
 two terms mean the same thing.  The keywords AUTHORIZATION ID in SQL
 and DB_HANDLE in RDO are also synonymous.  For more information see
 the Help topic on authorization_id.

 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.


 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.

Additional information available:

CREATE_SCHEDULECREATE_TRANSFERDROP_SCHEDULEDROP_TRANSFER
REINITIALIZESHOW_TRANSFERSTART_TRANSFER

Release NotesError msg doc

 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:DDAL020.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 Information

 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.

 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:

More Information

 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

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

Additional information available:

More Information

 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.

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

Additional information available:

More Information

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

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

Additional information available:

More Information

 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.

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

 transfer-attribute =

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

Additional information available:

More Information

 Displays information about the transfer definition, schedule
 definition, the transfer status, or all of these transfer attributes.

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

Additional information available:

More Information

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

 data-type =

 --+-> CHAR -+--------+---------------------------+-->
   |         +-> (n) -+                           |
   +-> VARCHAR (n) -------------------------------+
   +-> LONG VARCHAR ------------------------------+
   +-> TINYINT --------------+-----+--------+-----+
   +-> SMALLINT -------------+     +-> (n) -+     |
   +-> INTEGER --------------+                    |
   +-> QUADWORD -------------+                    |
   +-> LIST OF BYTE VARYING -+                    |
   +-> DECIMAL -+-+-----------------------------+-+
   +-> NUMERIC -+ +-> ( --> n -+--------+-> ) --+ |
   |                           +-> , n -+         |
   +-> FLOAT -+--------+--------------------------+
   |          +-> (n) -+                          |
   +-> REAL --------------------------------------+
   +-> DOUBLE PRECISION --------------------------+
   +-> DATE --------------------------------------+

Additional information available:

More Informationdomains

 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.

 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 authorization identifier that declares
 the schema as the default schema.  Specifying a default schema means
 that subsequent statements during the database attachment that refer
 to the default schema need not use an authorization identifier.

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

 Select More_Information to continue.

Additional information available:

More Information

 If you do not declare any schema, SQL declares the schema specified
 in the logical name SQL$DATABASE as the default schema, using the FOR
 FILENAME clause.

 If you declare a schema specifying an authorization identifier other
 than the one that declares the default schema, you must use that
 authorization identifier to qualify names of any schema entities to
 which you refer in SQL statements.  If you omit the authorization
 identifier, SQL assumes the table or view must be part of the default
 schema.  If there is no default schema and you omit the authorization
 identifier, 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 -+----------------++------------+--+
                          +-> INSERT ONLY -++--> TABLE --+  |
                          +-> READ ONLY ---++--> LIST ---+  |
    +---------------------------<---------------------------+
    |
    +-> CURSOR 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 list or into a dynamic cursor.

 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 also known as a dynamic positioned
 insert statement.

Additional information available:

FormatFormat

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

 Use the following syntax when you want to insert 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
ADADISUNSADAVARUNSAGGTBLCURALLSCHROLL
ALLSCHTABALTNOTOCBALTSCHATTALT_SCH_RDB_ERR
AMBHV_DECAMBTYP_DECAMB_KEYWORDANODBHAND
ANSIPROTONLARGCOUNTARGNOTNUMARIEXPEXP
ASSSTRLITATTMISSINGBADADJLOCKGRANBADBLOBBADBUFFERPOOL
BADCLUMPBADCOLLATIONBADCORATTBADCTXLEN
BADCTXTYPEBADCTXVERBADDBHANDBADDBKEY
BADDICTIONARYBADDTFMTBADEPILOGUEBADEPINAM
BADEXTENDIBLEBADFILEVERBADFLDTYPBADIDXMAP
BADINTERVALBADLANGUAGEBADLOGFILEBADLOGNAM
BADMAINTBADMETNAMBADMVIEWFLDBADMVIEWREL
BADMVIEWVEWBADMVRELSBADMVVIEWSBADNONEXTEND
BADPAGEFORMATBADPREPAREBADPROLOGUEBADPRONAM
BADPROTECTIONBADRECBUFBADROLMVFLDBADSEGSTRING
BADSNAPFILENAMEBADSTOGROUPBADSUPLVLBADTHRESHOLD
BADVAXCLUSNODESBADVERNUMBAD_ARRAYBAD_CDD_DEF
BAD_DBBAD_LENGTHBAD_LEVELBAD_NAME
BAD_PRECISIONBAD_SCALEBAD_TOKENBAD_TXN_STATE
BAD_VERSIONBASROWDELBINSCAFACBIT_FIELDBOOEXPEXP
BUGCHKCABORTCANTDOVALXPRCDDERRCDDUNKPROT
CDDVERERRCHECKOPTROCHGINDMAPCHGINDMAPSTP
CHR_TOO_SHOCHR_TOO_SMACIRCTYPECLOSERRCMDINTR
CMPBYINVWCMPBYMVMETOOCMPBYWNRLCMPBYWNVW
CNTSPNSUBCOLEXISTSCOLLSTINVCOLNOTFUNCOLNOTNUL
COLNOTSSCOLNOTUPDCOLNOTVALCOMPNOTRANS
COMTOOLONCONALREXICONAMBIGCONCHAILL
CONDICREQCONNOTDEFCONNOTSUPCONREAATT
CONSNAATTCONTPREQCONTRIACTCONVARDEF
CONVARUNDCORREFFUNCRE_STO_ERR_SCHCS_ERR
CTXIGNOREDCTXPARMNOTALLCURALRDCLCURALROPE
CURNAMEXICURNOTOPECUROFNOTCUROFREQCUROFSTA
CURSTMTTXNCURTWOOPENCURUSEINVDATCONERR
DATNOTSUPDATTYPUNKDBHANDUNKDBHDLREQ
DBINUSEDBKAMBIGDBKTOOBIGDB_EXISTSDB_HANDEC
DB_HANDEC2DB_HANLONDB_IN_TXNDCLBEFEXE
DCLDATBEFDDALERRDDALFMTUNKDDALNOTINS
DDLPARAMDDNOTSUPPDECCURINTODEFCONMOD
DEFDBDECDEFVALINCDEFVALNOTCBDEFVALUNSDEGMODSPC
DELBACKUPDELLSTDYNCURDEPIMPCASDEP_FEATURE
DIC_DB_CHG1DIC_DB_CHG2DIFFSCHVIEWDIGNUMPIC
DPBFMTUNKDROP_IDXDROP_STOMAPDROP_TRIG
DROP_VIEWDRO_SCH_RDB_ERRDTFMTTOOBIGDTONCEEACH
DUPFLDDEFDUPPROCNAMDUPREFACTDUPVAR
DYNSIZARREMPMSGVECENDENUM_VAR
ERRATTDECERRATTDEFERRCRESCHERRDET
ERRINCPATHERRSYMDELERRSYMREPES_ILL_RPT
EVACLAUNSEXESELSTAEXPNUMLITEXPQUEXPR
EXP_CDD_NODATAEXP_CDD_NOEXTEXTRADATAEXTREPONESCH
FETNOTDONFIELD_EXISTSFKCONSNOTCBFLDAMBIG
FLDNOTBCKFLDNOTCRSFLDNOTDEFFLDNOTINREL
FLUINPBUFFORCOLNMASSFORCOLNMDECLFORCOLNODECL
FORPASLENFORTABNODECLFUN_VARGARBLEDGETCRESEG
GFLOATHEXSTREVEHI_ORD_LOSHVNOTDECL
HV_NOT_INIDMISSINGILLBEGINILLCHARILLDATLENILLEXEIMM
ILLFLOLENILLFROMILLHEXNUMILLINTLENILLPICSTRILLSTRCONT
IMPL_DIMIMP_CDD_NODATAIMP_IDXNOTCREIMP_IDXNOTDRO
IMP_IDX_CONFLICTIMP_IDX_TWICEIMP_STANOTDROIMP_STMNOTCRE
IMP_STMNOTDROIMP_STO_CONFLICTIMP_STO_MAP_CONFLICT
IMP_STO_MAP_TWICEIMP_STO_TWICEIMP_TRA_BEG
IMP_TRA_ENDINCNOTRECINC_DAT_TYPINDEXTS
INDFIXINTINDNOTDEFINDSHOINTIND_EXISTSINFODET
INPUTERRORINSCOLALRINS_INTO_ROINS_MUST_INS
INTIGNSYSINTNOTSYSINTONOTALWINTONOTQUALINTVALLOW
INTVALOVRINVACLINVARRSUBINVATTVALINVCHAINP
INVCHANUMSTRINVCOLLSTINVCOLSPCINVCOMLININVCONS
INVCORRSLINVDATCONINVDBKREFINVDISXPR
INVESCVALINVFLDINVFUNREFINVHVDECLINVINDEX
INVLENHVINVNODESIZEINVNUMLITINVNUMSTRPRE
INVOBJFILINVORDNUMINVPERCENTFILLINVPRIVINVPRIVNAMES
INVQUALINVREFCLAINVRELVIEWINVRNGINVSEGVAL
INVSELLISINVSELSTARINVSQLCODEINVSSCONV
INVSSHANINVSTRLENINVTRGINVTRISTMTINVTYPEINVVALLIS
IOERRORISQLINTOJUNONLINKEYTOIDENTLANFILEXTLANSWIVAL
LANUNSDSCDTPLANUNSDTPLENMISMATLIMFIXINT
LINETOOLONGLISTNOTVALLIT_EXCEPTLOOK_FOR
LOOK_FOR_CONLOOK_FOR_FINLOOK_FOR_STMTLOOK_FOR_STT
LOOK_FOR_UNTERMLOW_ORD_LOSLSTCURSTALSTNOTNUL
LSTREFAMBMAXFLDPRTSTRMAXNESEXCMAXRELEXC
MINGTRMAXMISREQVALMIXTABLISMOVENOCOLS
MULDIMARRMULSPECATRMULTSPECATRMULT_STRUCT
MUL_UICMVMULTITARGMVRELABSNTNAMCONFNAMTOOBIG
NEG_DIMNESFUNINVNESINCFILNESQRYEXPNO1ST
NOAGGALLNOALTERNOANYALLNOBATCHUPDATENOBATUPDNOBCKFIL
NOBCKTRNSNOBUCTXPARMNOBUUSINGCTXNOCDD
NOCDDALTNOCDDRESNOCDDUPDATNOCMPBYRESNOCOLALL
NOCOLLSTNOCOLNAMNOCOLRESNOCONNAMNOCONRES
NOCORRCOLNOCPRIRESNOCUROFNODATDIVNODATRES
NODBHALWNODBKALLNODBKGRONODBNAME
NODEFDBNODISTINCTNODUPLIVIEWNOFILLISTNOFLDRES
NOFSTINREPTNOGROUPNOIDXRESNOIMPTXNNOINCDICNOITEMDEF
NOLANGFILNOMAPRESNOMATCHKEYNOMLTIMVNOMLTIMVIEW
NOMODFILNOMVRALLNOMVVROLNONCONARRNONOVAL
NONSTAAMBNONSTACASNONSTACOBNONSTACOL
NONSTACONNONSTACUCNONSTACURNONSTADIS
NONSTADTPNONSTADYNNONSTAHVNONSTANAM
NONSTAOKWNONSTAPHYNONSTAQUONONSTASCL
NONSTASMNONSTASYNNONSTATXNNONSTAUNI
NONSTAVIANOOPENCURNOORDERNOPASQLDA
NOPRECOMPSELNOPRIMKEYNOPROCNOPRVMVIEW
NOPRVMVRELNOPRVREPLINOPRVROLMVRNORDBPRIV
NOREDINREPTNORELFOUNORELRESNOREMVERNORETURN
NOROCOLNORTPARMNOSCHALTNOSEGSTRAREANOSELALLNOSELXPR
NOSORTINREPTNOSPRIRESNOSQLCANOSQLCODENOSTRDEF
NOSTRNAMNOSUCHCURNOSUCHDATEFMTNOSUCHLANG
NOSUCHPROCNOSUCHTIMEFMTNOSUPREPLINOTAVIEW
NOTDB2NOTDB2DURNOTDB2FNNOTFOUNDNOTGROFLD
NOTHVDECLNOTINSCURNOTINTBLCURNOTLISTCOL
NOTLSTCURNOTPRIRESNOTRGRESNOTSAMETBL
NOTTBLCURNOTUSEINDNOTYPESNOT_A_DB
NOT_CDD_DBNOT_SAME_CONTEXTNOT_SCH_IDNOUNION
NOVIERESNOVIEWINREPTNOWHERENO_CDDACCNO_COMMAND
NO_DCLTXNNO_DECIMALNO_DESCENDINGNO_DMLPLAN
NO_ENDCOMNO_ENDEXECNO_FILFNDNO_INCFND
NO_NUMERICNO_PLNFNDNO_SQLDANO_SUCH_FIELD
NO_TRIGGER_VALSNO_TXNOUTNO_UNSNUMERICNSEGBLR
NULLNOINDNUMCMPTXTNUMHVSNOTNUMITESEL
NUM_TO_DATEONEEPERMONETXNMODONLFIRPRE
ONLFIRVARONLONEDBONLONETRNONLVALLSTONLY1LISTONLY1TBL
ONLYONEPSECTOPENERROPRSTK_OVRFLOPARAMNOTSTR
PARAMQUALPARBADCLAPARBADDATPARBADLEN
PARBADSCAPARBINSCAPARMLISTREQPARSE_STACK_OVERFLOW
PASRECUNSPASVARUNSPATH_NAM_REQPHYBACDAT
PKCONSNOTCBPKGNAMCHGPKNOTNULLPREFORSTR
PREMATURE_EOFPREPNOCTXSTRPRESTAOPEPRIKEYEXI
PRINT_SSIDPROCNOCAPRPSELINTOPRVERRSDTPUNK
PTR_VARPUTOPESEGQUAINVVALQUANOVALRDBVMSONL
REANOWRTREAONLATTRECEXCMAXREFKEYCOL
REFKEYNUMRELAMBIGRELNOTDEFREL_EXISTS
REMNOTALWREORGONLALTSMRESABORTRESERVED_WORD
RETRYPOSREVENTANSSCHNOABSTIMSEGAREERR
SEGSTREXPSELMORVALSEVERRDETSHDESCEND
SHINDFLDSIZESHINDMAPVALSHINDMAPVAL2SHOTABMAPDR
SMA_DAT_TYPSPACREQSPANOTVALSQLDANOTSQLDATA
SQLTYPESSTOOBIGSTANOTDEFSTANOTSELSTAREQCOL
STARNOTALLSTAROCURSTATWOCURSTOCOLERR
STOCOLUKNSTOTABUKNSTRARRAYSTRCVTNUM
STRINXPRSTRLITEXPSTRLITMISQUOSTRMORELESTRTOOBIG
STRTOOLONSTRXPREXPSUBNOGBSUBTOOVAL
SYM_EXPSYNTAX_ERRSYSPAGFORSYSPAGUNIS_FLDB_NS
S_FLDB_SS_FLDNLS_FLDNUS_FLDPS_STOAREA_READONLY
S_STOAREA_READWRITES_TRANSBRIEFS_TRANSFCOMMENT
S_TRANSFDEFS_TRANSFDEFINERS_TRANSFDEFNONES_TRANSFDELTA
S_TRANSFDESTDBS_TRANSFEPILOGS_TRANSFERSS_TRANSFINF1
S_TRANSFINF2S_TRANSFLASTS_TRANSFLINES_TRANSFLOGFILE
S_TRANSFMODEES_TRANSFMODEERS_TRANSFMODERS_TRANSFNEXT
S_TRANSFNOEPIS_TRANSFNOLOGS_TRANSFNONES_TRANSFNOPRIV
S_TRANSFNOPROS_TRANSFNOSTSS_TRANSFPROLOGS_TRANSFRETRIED
S_TRANSFRETRYS_TRANSFSCHS_TRANSFSCHDAYS_TRANSFSCHDLT
S_TRANSFSCHDPWS_TRANSFSCHDPW2S_TRANSFSCHMONS_TRANSFSCHNONE
S_TRANSFSCHONCS_TRANSFSCHWEKS_TRANSFSOURCES_TRANSFSRCDB
S_TRANSFSRCNOHS_TRANSFSTARTS_TRANSFSTATUSS_TRANSFSTS
S_TRANSFSTSACTS_TRANSFSTSNONES_TRANSFSTSRETS_TRANSFSTSSCH
S_TRANSFSTSSSPS_TRANSFSTSUNSS_TRANSFSTSWTRS_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_WAIT_INTERVALTBLCOLAFTTBLCURDYN
TBLNOTCURTHRIGNSYSTHRNOTSYSTOKINSBEF
TOKTOOBIGTOOBIGBLRTOOMANYTBLTRAACT
TRAACT_1TRAACT_2TRAACT_3TRADBPNEWONLTRAHDLINV
TRAMODSPCTRANOTOWNERTRANSFDISTREPTRANSFGRPBY
TRANSFHAVINGTRANSFSUBQRYTRANSFUNIONALLTRATOEXEXTR
TRATOEXPRIVTRATOEXRDBTREE_OVRFLOTRNNOTBLS
TRNNOVIEWSTXNNOTLONGTXN_HNDL_IGNOREDUKN_ALT_OPT
UNAOBTDSRUNBDECFILUNBTMPFILUNDEFVAR
UNDPARAMUNICONSNOTCBUNIONEXTROLLUNISELLIS
UNKTYPEUNMATENDUNSCOMPBYUNSDATATYPE
UNSDATXPRUNSDB2PRIVUNSDSCCLAUNSDTPCVT
UNSIGNED_VARUNSNUMXPRUNSPLIATTUNSSTRXPR
UNSSUPDATUNSUPOPUNSUPVERUNTSTRUPDCOLPRIV
UPDINSCURUPDREACURUSERINVIEWUSINGCTXNOTALL
USRDEFTYPVECNOTINDVEWNOTDEFWAIMODSPC
WARDETWARNINGCBWHYTWICEWISH_LISTWRICIRREF
ZABORTZEROSIZE

 Triggered statement is not in the same schema as the trigger

 Explanation:  You specified a triggered statement which uses a
 different      schema than the schema the trigger is a part of.
 This is not

 User Action:  Specify only triggered actions which execute in
 the schema in  which the trigger is defined.

 No matching access control entry found

 Explanation:  In a protection command that refers to an existing
 access control entry, you specified identifiers that did not
 match any existing entry.

 User Action:  Use SHOW PROTECTION to see what the access control
 list currently looks like, and correct your command.

 ACE identifier stack overflow during ACE parsing

 Explanation:  You included too many identifiers in an
 expression.  The identifier stack for the access control entry
 (ACE) overflowed during parsing.

 User Action:  Simplify the access control entry that caused the
 error.

 ACE identifier stack underflow during ACE parsing

 Explanation:  The access control entry (ACE) identifier stack
 underflowed during ACE parsing.  This happens when identifiers
 are not stored in the stack appropriately.

 User Action:  Submit a software performance report (SPR) with
 the Rdb/VMS interchange file (.RBR).

 Host variable <text> is based on a type that uses discriminamts

 Explanation:  The host variable you referred to is based on a
 type which uses Ada discriminants.  SQL does not support types
 which include discriminants

 User Action:  Use a different type defintion.

 Host variable <text> is based on a record type that uses
 variants

 Explanation:  The host variable you referred to is based on a
 record type which uses Ada variants.  SQL does not support types
 which include variants.

 User Action:  Use a different type defintion.

 Table cursor, <text>, cannot have list cursors because it
 contains an aggregate or UNION

 Explanation:  The table cursor referenced in the WHERE CURRENT
 OF clause of a list list cursor was defined using an aggregate
 or union expression.

 User Action:  Change the table cursor to no specify an aggregate
 or union expression.

 All schemas may be moved only by EXTRACTION ROLLUP transfers

 Explanation:  You have specified *.* in the move tables clause
 of a transfer which was an extraction or replication transfer.

 User Action:  Reenter the CREATE TRANSFER statement with a
 differene MOVE clause.

 All tables must be moved if all schemas are moved

 Explanation:  The move clause must be *.* or xxx.*, not *.xxx.

 User Action:  Reenter the CREATE TRANSFER statement with a
 different MOVE clause.

 ALTER TABLE may not be used to change a column to computed

 Explanation:  The ALTER clause of the ALTER TABLE statement was
 used to change an existing column with a data type to a computed
 column.

 User Action:  Use the DROP clause of the ALTER TABLE statement
 to drop the existing column and the ADD clause to add a computed
 column.

 You cannot use the ALTER SCHEMA statment on a declared schema

 Explanation:  You attempted to alter a schema that was already
 declared.

 User Action:  Either remove the ALTER SCHEMA statment or make
 sure the       schema to be altered has not been declared.

 ALTER SCHEMA is only supported with Rdb/VMS Version 3.0 or later

 Explanation:  The ALTER SCHEMA requires Rdb/VMS V3.0.  SQL will
 not alter schemas without Rdb/VMS Version 3.0 or later installed
 on the system.

 User Action:  Install the Rdb/VMS Version 3.0 or later.

 Host variable <text> was ambiguously defined

 Explanation:  You declared a host variable ambiguously by using
 the same name in two host variable declarations.

 User Action:  Change the name or level of one of the
 definitions.

 Host variable <text> was based on an ambiguously defined type

 Explanation:  You declared a host variable which was based on a
 type.  The type is ambiguous because two or more type
 declarations use the same name.

 User Action:  Change the name or scope of one of the
 definitions.

 Ambiguous keyword abbreviation

 Explanation:  You used an ambiguous abbreviation.

 User Action:  Specify the entire keyword.

 Another schema already declared with authorization identifier
 <text>

 Explanation:  You specified in the DECLARE SCHEMA statement the
 same authorization identifier as in a previous DECLARE SCHEMA
 statement.

 User Action:  Either issue a FINISH statement and try the same
 DECLARE SCHEMA statement, or enter the DECLARE SCHEMA statement
 again with a different authorization identifier.

 This statement may only refer to database with ANSI protection

 Explanation:  You tried to execute a SHOW statement which is
 only for ANSI style protections on a database which uses ACL
 style protections.

 User Action:  Only use this statement with ansi style
 protections.

 Procedure <text> expected <value> parameters, was passed <value>

 Explanation:  The module language procedure was not passed as
 many parameters as it expected.  This may be because the
 /CONTEXT qualifier was or was not specified when the module was
 compiled, or because the procedure call and procedure
 declaration do not have the same number of parameters.

 User Action:  If a context parameter is being passed, make sure
 that the /CONTEXT qualifier is specified on module compilation.
 Otherwise, make sure that the procedure call and declaration
 specify the same number of parameters.

 Argument must be numeric

 Explanation:  The expression for an AVG or SUM function must be
 numeric.

 User Action:  Change the value expression to contain only
 numeric fields, or remove the function.

 Expected arithmetic value expression

 Explanation:  You supplied a predicate where SQL expected to
 find an arithmetic value expression.

 User Action:  You must use an arithmetic value expression in
 this context.

 Numeric literal is assumed to be text

 Explanation:  You tried to store a numeric literal into a text
 column or compare a numeric literal to a text column.  SQL
 assumes the string is a text literal and converts it for the
 storage or comparison.  Note that each digit in the numeric
 literal, including leading zeroes, is converted to text.  For
 instance, 001 and 1 represent the same number, but are converted
 to different literals ("001" and "1").

 User Action:  None.  However, it is good programming practice to
 convert the numeric literal to a string literal by enclosing it
 in quotes.

 invalid or missing attributes

 Explanation:  Internal error -- a required attribute (such as
 the data type in a GLOBAL FIELD clump) is missing.

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.

 ADJUSTABLE LOCK GRANULARITY clause is not allowed in the CREATE
 TRANSFER statment.

 Explanation:  You have specified an ADJUSTABLE LOCK GRANULARITY
 clause as an attribute for the target database in a CREATE
 TRANSFER statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 ADJUSTABLE LOCK GRANULARITY clause.

 unable to import a list

 Explanation:  Error from Rdb$CREATE_SEGMENTED_STRING.  See the
 following message for more information.

 User Action:  If the nature of the problem is not obvious,
 submit an SPR with a copy of the Rdb/VMS interchange file (.RBR)
 that caused the error.

 BUFFERPOOL clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified the BUFFERPOOL clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 BUFFERPOOL clause.

 invalid clump type encountered

 Explanation:  Internal error - bad data in the Rdb/VMS
 interchange file (.RBR).

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.

 COLLATION SEQUENCE clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified the COLLATION SEQUENCE clause
 as an attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 COLLATION SEQUENCE clause.

 invalid core attribute <hex-value>, <hex-value> in .RBR file

 Explanation:  Internal error - bad data in the Rdb/VMS
 interchange file (.RBR).

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.

 Illegal length value found in context structure

 Explanation:  The LENGTH field of the context structure passed
 to the SQL procedure was illegal.  VAX SQL supports only the
 global tid, which has a length of 16 (symbolically DDTM$S_TID).

 User Action:  Change the HLL code to pass a context structure
 whose only length is 16 (DDTM$S_TID).

 Illegal type value found in context structure

 Explanation:  The TYPE field of the context structure passed to
 the SQL procedure was illegal.  VAX SQL supports only the
 SQLCONTEXT$K_GLOBAL_TID type.

 User Action:  Change the HLL code to pass a context structure
 whose only type is SQLCONTEXT$K_GLOBAL_TID.

 Unsupported version of context structure

 Explanation:  The VERSION field of the context structure passed
 to the SQL procedure was unsupported.  VAX SQL supports only the
 SQLCONTEXT$K_VERSION1 version.

 User Action:  Change the HLL code to pass a context structure
 whose only version is SQLCONTEXT$K_VERSION1.

 Authorization identifier <text> not used by this query

 Explanation:  You used an authorization identifier to qualify a
 reference to a column and that authorization identifier was not
 specified in the FROM clause of the query.

 User Action:  Either remove the authorization identifier that
 qualifies the select-list item or specify the same authorization
 identifier as specified in the FROM clause of the query.

 DBKEY SCOPE clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified the DBKEY SCOPE clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 DBKEY SCOPE clause.

 DICTIONARY clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified the DICTIONARY clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 DICTIONARY clause.

 Date or time format is not set up properly.

 Explanation:  You entered a SHOW DATE FORMAT statement, but
    LIB$DT_FORMAT is not properly defined.

 User Action:  Check the definition of LIB$DT_FORMAT.  If it is a
 process logical, it should be changed.  If it is a group
       or system logical, contact your system manager to change
 it.

 only one epilogue file clause can be specified per transfer

 Explanation:  You specified more than one epilogue file clause
 in the CREATE TRANSFER statement.  This is not permitted.

 User Action:  Reenter the CREATE TRANSFER statement, specifying
 only one EPILOGUE IS or NOEPILOGUE clause.

 invalid epilogue file name

 Explanation:  You entered an invalid epilogue file name.

 User Action:  Refer to the explanation in the user action
 section of the secondary error message.

 EXTENDIBLE clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified the EXTENDIBLE clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 EXTENDIBLE clause.

 incompatible .RBR file type

 Explanation:  This version of SQL cannot import a database from
 this Rdb/VMS interchange file (.RBR).

 User Action:  Use a version of RDO that corresponds to the
 version of RDO that created this file.

 source fields of target relation <text> field number <value>
 have different types

 Explanation:  In a CREATE TRANSFER statement of an EXTRACTION
 ROLLUP transfer, you have entered MOVE RELATION clauses with the
 same target relation name and specified fields with the same
 names but of different data types in the source databases.

 User Action:  Reenter the CREATE TRANSFER statement by
 specifying fields of the same data type in all the MOVE RELATION
 clauses with the same target relation.

 Fields specified for partitioning btree do not agree with fields
 for index

 Explanation:  You named fields to partition a btree index but in
 an incorrect order.

 User Action:  Review the statement and specify it again.

 INTERVAL clause is not allowed in the CREATE TRANSFER statement.

 Explanation:  You have specified an INTERVAL clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 INTERVAL clause.

 Language <text> not properly set up.

 Explanation:  SQL attempted to retrieve month or weekdays from
 the    logical name table LNM$LANGUAGE_xxx for language xxx,
   but could not retrieve a value.

 User Action:  Contact the sytem manager to make sure everything
 has been properly set up.

 only one log file clause can be specified per transfer

 Explanation:  You specified more than one log file clause in the
 CREATE TRANSFER statement.  This is not permitted.

 User Action:  Reenter the CREATE TRANSFER statement, specifying
 only one LOG FILE IS or NOLOG clause.

 invalid log file name

 Explanation:  You entered an invalid log file name.

 User Action:  Refer to the explanation in the user action
 section of the secondary error message.

 Database is an unsupported maintenance release for the current
 version

 Explanation:  The maintainance release number and the version
 number of the database that you just attached to forms an
 unknown combination.

 User Action:  Check to make sure that you are running with the
 correct versions of Digital-supported database products for the
 SQL interface to Rdb/VMS.  Correct versions are listed in the
 Rdb/VMS Installation Guide.

 Metadata names must end in A - Z or 0 - 9

 Explanation:  The name given in a data manipulation or
 definition statement ended with a dollar sign ($) or underscore
 (_).  These symbols are not allowed.

 User Action:  Specify a valid name.

 field <text> of relation <text> must be moved for view <text>

 Explanation:  You attempted to transfer a view without
 transferring a field to which the view refers.  You must also
 explicitly transfer in the CREATE TRANSFER statement all
 relevant fields of relations to which the view refers.

 User Action:  Reenter the CREATE TRANSFER statement, adding the
 required field to the appropriate MOVE RELATION clause.

 underlying relation <text> of view <text> must also be moved

 Explanation:  You attempted to transfer a view without
 transferring the relations to which the view refers.  You must
 explicitly transfer the relations to which the view refers in
 the CREATE TRANSFER statement.

 User Action:  Reenter the CREATE TRANSFER statement adding the
 required MOVE RELATION clause.

 underlying view <text> of view <text> must also be moved

 Explanation:  You attempted to transfer a view without
 transferring other views that underlie the view you want to
 transfer.  You must explicitly transfer the views to which the
 view refers in the CREATE TRANSFER statement.

 User Action:  Reenter the CREATE TRANSFER statement adding the
 required views to the MOVE VIEW clause.

 move-relations-clause is allowed only once in CREATE TRANSFER

 Explanation:  You specified more than one move-relations-clause
 in a CREATE TRANSFER statement.  Possibly you did not separate
 the MOVE RELATION clauses with semicolons.

 User Action:  When you use a CREATE TRANSFER statement, group
 all the MOVE RELATION clauses together and separate them with
 semicolons.

 move-views-clause is allowed only once in CREATE TRANSFER

 Explanation:  You entered more than one move-views-clause in a
 CREATE TRANSFER statement.  Only one move-views-clause is
 allowed in a CREATE TRANSFER statement.

 User Action:  Combine all MOVE VIEWS clauses into one list and
 separate the view names with commas.

 NONEXTENDIBLE clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified the NONEXTENDIBLE clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 NONEXTENDIBLE clause.

 PAGE FORMAT clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified a PAGE FORMAT clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 PAGE FORMAT clause.

 Cannot use DESCRIBE or EXECUTE on a statement that is not
 prepared

 Explanation:  You attempted to use a DESCRIBE or EXECUTE
 statement that named a statement which was not successfully
 prepared.

 User Action:  Prepare the statement before calling DESCRIBE or
 EXECUTE.

 only one prologue file clause can be specified per transfer

 Explanation:  You specified more than one prologue file clause
 in the CREATE TRANSFER statement.  This is not permitted.

 User Action:  Reenter the CREATE TRANSFER statement, specifying
 only one PROLOGUE IS or NOPROLOGUE clause.

 invalid prologue file name

 Explanation:  You entered an invalid prologue file name.

 User Action:  Refer to the explanation in the user action
 section of the secondary error message.

 PROTECTION clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified the PROTECTION clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 PROTECTION clause.

 NUMBER OF RECOVERY BUFFERS clause is not allowed in the CREATE
 TRANSFER statement.

 Explanation:  You have specified the NUMBER OF RECOVERY BUFFERS
 clause as an attribute for the target database in a CREATE
 TRANSFER statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 NUMBER OF RECOVERY BUFFERS clause.

 MOVE RELATION clauses of target relation <text> have different
 fields

 Explanation:  In a CREATE TRANSFER statement of an EXTRACTION
 ROLLUP transfer, you have entered a MOVE RELATION clauses with
 the same target relation name but specified a different set of
 fields in each clause.

 User Action:  Reenter the CREATE TRANSFER statement by
 specifying the same set of fields in all the MOVE RELATION
 clauses with the same target relation.

 SEGMENTED STRING clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified the SEGMENTED STRING clause as
 an attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 SEGMENTED STRING clause.

 SNAPSHOT_FILENAME clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified a SNAPSHOT_FILENAME clause as
 an attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 SNAPSHOT_FILENAME clause.

 STOGROUP clause is not allowed in the CREATE TRANSFER statement.

 Explanation:  You have specified the STOGROUP clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 STOGROUP clause.

 Attached database has unknown support level.

 Explanation:  The database you just attached to has an unknown
 support level.

 User Action:  Check to make sure that you are using
 Digital-supported database products for the SQL interface to
 Rdb/VMS.

 THRESHOLDS clause is not allowed in the CREATE TRANSFER
 statement.

 Explanation:  You have specified a THRESHOLDS clause as an
 attribute for the target database in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 THRESHOLDS clause.

 NUMBER OF VAXCLUSTER NODES clause is not allowed in the CREATE
 TRANSFER statement.

 Explanation:  You have specified a NUMBER OF VAXCLUSTER NODES
 clause as an attribute for the target database in a CREATE
 TRANSFER statement.

 User Action:  Reenter the CREATE TRANSFER statement without the
 NUMBER OF VAXCLUSTER NODES clause.

 Attached database has unsupported version number.

 Explanation:  The database you just attached to has a version
 number that is not supported by this version of SQL.

 User Action:  Check to make sure that you are running with the
 correct versions of Digital-supported database products for the
 SQL interface to Rdb/VMS.  Correct versions are listed in the
 Rdb/VMS Installation Guide.

 Host variable <text> contains an array syntax error in its
 declaration.

 Explanation:  The named variable is defined as a C array, but is
 either missing the closing "]" or contains a non-numeric
 dimension.

 User Action:  Correct the syntax of the declaration and
 recompile the program.

 CDD$DEFAULT is not valid, data dictionary default is now
 CDD$TOP.

 Explanation:  Your logical name CDD$DEFAULT is not acceptable to
 the data dictionary.  The data dictionary will be used, but your
 default is set to CDD$TOP.

 User Action:  Define a valid CDD$DEFAULT.

 Data dictionary description of current schema is corrupt

 Explanation:  The data dictionary description of the schema is
 missing the RDB$INSTANCE node.

 User Action:  Verify that the schema itself has not been
 corrupted.  If it has, recreate the schema.

 Negative length specified for column <text>

 Explanation:  You specified a length for a character or varchar
 column that was less than zero.

 User Action:  Change the length to a positive number.

 CONSISTENCY LEVEL <value> is illegal

 Explanation:  Only values 2 and 3 are allowed for consistency
 level.

 User Action:  Enter 2 for concurrency; enter 3 for consistency

 Identifiers and names may not exceed 31 characters in length

 Explanation:  The name given in a data manipulation or data
 definition statement was longer than the permitted limit.

 User Action:  For data definition statements, specify a shorter
 name.  For data manipulation statements, consult your database
 design specifications to find the correct name.

 Invalid precision specified for column <text>

 Explanation:  The precision specified for a DECIMAL or NUMERIC
 column is less than or equal to zero.  Or, the precision
 specified for a FLOAT column was less than zero or greater than
 15.  Or the precision contained a decimal point.

 User Action:  Change the precision to a valid value.

 Negative scale specified for column <text>

 Explanation:  The scale specified for a column is less than
 zero.

 User Action:  Change the scale to a positive number.

 <text> is not a valid SQL language element

 Explanation:  The indicator string is neither a predefined
 language element (i.e.  a keyword, delimiter or operator) not a
 valid SQL name.

 User Action:  Use a valid SQL language element.

 Invalid transaction state.  Transaction already started.

 Explanation:  A SET TRANSACTION statement was executed, but it
 was not the first statement executed in the transaction.

 User Action:  Make the SET TRANSACTION statement the first
 statement to be executed.

 This database system does not support this statement

 Explanation:  This statement uses a DSRI feature which is not
 supported by   all versions of all DSRI database systems.  You
 tried to       execute this statement  using a version of a
 database system        which does not support this feature.

 User Action:  Use a simpler statement, or a different base
 system version.

 Row containing list has been deleted

 Explanation:  An attempt was made to fetch or insert into a list
 cursor where the row containing the list has been deleted.

 User Action:  Do not delete the row containing the list or
 simply close the list cursor.

 Host variable <text> has a binary scale factor

 Explanation:  The host variable is a PL/I fixed binary data type
 with a nonzero binary scale factor.  SQL supports only decimal
 scale factors.

 User Action:  Either change the scale factor to zero, or change
 the data type to fixed decimal.

 Host variable <text> is a bit field which is illegal in SQL
 statements.

 Explanation:  The named variable is defined as a C bit field.
 Such fields are not legal in SQL statements.

 User Action:  Use a different variable.

 Expected a predicate

 Explanation:  Either a numeric or string value expression was
 found where SQL expected a predicate.

 User Action:  You must use a predicate in this context.

 There has been a fatal error.  Please submit an SPR.  No dump
 was produced

 Explanation:  A fatal error has occurred.

 User Action:  Submit an SPR with information about the
 circumstances under which the bug occurred.  Note that
 SQL$_BUGCHECKs do not produce dumps as RDB$_BUGCHECKs do.

 User entered Control-C to abort statement

 Explanation:  You typed a Control-C to abort the current
 statement.

 User Action:  None.

 Value expressions may not be moved by CREATE TRANSFER

 Explanation:  The user entered a value expression in the select
 list of a select expression in the move tables clause of the
 CREATE TRANSFER statement.  This is not allowed.

 User Action:  Move only columns using CREATE TRANSFER.  Use a
 prologue file to define a view on the target database which
 computes the value expression from the columns moved.

 Error occurred during attempt to use data dictionary.  Data
 dictionary will not be used

 Explanation:  An error occurred when SQL attempted to access the
 data dictionary.

 User Action:  Refer to following data dictionary messages for
 more information.

 Unknown data dictionary protocol <text>

 Explanation:  The protocol in the data dictionary was not
 correct.

 User Action:  Try to recreate the data dictionary.  If the data
 dictionary is still corrupt, submit an SPR.  Try invoking it
 with the file name.

 Found data dictionary core_level <value> was expecting <value>

 Explanation:  The core_level in the data dictionary was not
 correct.

 User Action:  Try to recreate the data dictionary.  If the data
 dictionary is still corrupt, submit an SPR.  Try invoking it
 with the file name.

 You specified WITH CHECK OPTION for read only view <text>

 Explanation:  You specified the WITH CHECK OPTION for a view
 which is based         on a read only select expression.  You
 should specify         the WITH CHECK OPTION only for a read
 write view.

 User Action:  Remove the WITH CHECK OPTION clause from this view
 definition,    or make the select expression specify an
 updatable select       expression.

 This index was previously specified with a STORE clause.
 Continue?  [N]

 Explanation:  You are specifying an ALTER INDEX statement
 without a STORE clause, which places the index into the
 RDB$SYSTEM storage area.  The index was previously specified as
 being stored in a different area.  SQL$ is confirming whether
 you want the index placed in the RDB$SYSTEM storage area.

 User Action:  An affirmative reply (Y or YES) causes the
 operation to continue.  A negative reply (a carriage return, N,
 or NO) terminates the operation.

 Terminating operation at user's request

 Explanation:  See above.

 User Action:  None.

 Character length of column <text> is too short

 Explanation:  The character string length is too short to
 contain all possible   converted data already stored in the
 column.

 User Action:  None.  This is a warning message only.

 The string length of column <text> is too small

 Explanation:  The length of the character string is too small to
 handle         all possible numeric data that might already be
 stored in      the table.

 User Action:  None.  This is a warning message only.

 Host variable <text> is based on a type which was used in its
 own definition

 Explanation:  You referred to a host variable which is based on
 a type.  The type was not validly defined because it was based
 on itself.

 User Action:  Fix the type definition.

 error detected when closing .RBR file

 Explanation:  See the message that follows for details.

 User Action:  In the absence of other error messages, the
 database has probably been imported successfully.

 this statement is not allowed in a transaction

 Explanation:  You entered a statement that cannot be used when a
 transaction is outstanding.

 User Action:  Commit or rollback the transaction and try the
 statement again.

 view <text> cannot be transferred because of invalid computed
 field <text> in relation <text>

 Explanation:  In a CREATE TRANSFER statement, you are attempting
 to move a view which references a COMPUTED_BY field which
 contains an unsupported value expression.

 User Action:  Reenter the CREATE TRANSFER statement and omit the
 view that contains the COMPUTED_BY field that uses the
 unsupported value expression.  Refer to the CREATE TRANSFER
 statement in the Data Distributor Handbook for information on
 what value expressions are supported for a COMPUTED_BY field.

 Column <text> in table <text> may not be moved without column
 <text>

 Explanation:  You included a column to be transferred that
 relies upon another column in the table.  This column must also
 be moved.

 User Action:  Re-enter the transfer definition including all
 necessary columns.

 Invalid computed field <text> will not be transferred from
 relation <text>

 Explanation:  In a CREATE TRANSFER statement, you are attempting
 to move a view which references a COMPUTED_BY field that
 contains an unsupported value expression.

 User Action:  Reenter the CREATE TRANSFER statement and omit the
 view which contains the COMPUTED_BY field that uses the
 unsupported value expression.  Refer to the CREATE TRANSFER
 statement in the Data Distributor Handbook for information on
 what value expressions are supported for a COMPUTED_BY field.

 view <text> will not transfer invalid computed field <text> from
 relation <text>

 Explanation:  In a CREATE TRANSFER statement, you are attempting
 to move a view which references a COMPUTED_BY field which
 contains an unsupported value expression.

 User Action:  Reenter the CREATE TRANSFER statement and omit the
 view that contains the COMPUTED_BY field that uses the
 unsupported value expression.  Refer to the CREATE TRANSFER
 statement in the Data Distributor Handbook for information on
 what value expressions are supported for a COMPUTED_BY field.

 Cannot spawn subprocess

 Explanation:  The preprocessor was unable to spawn a subprocess
 to compile the program.

 User Action:  Read the next message and determine what to do.

 Column <text> is named more than once in table <text>

 Explanation:  You attempted to create a table or view with using
 a column name more than once.

 User Action:  Choose a different name for each column.

 A column list is not allowed in an INSERT LIST CURSOR statement

 Explanation:  A column list was supplied for an INSERT LIST
 CURSOR statement.

 User Action:  Remove the column list.

 Column <text> named outside a function in a SELECT with HAVING
 but no GROUP BY

 Explanation:  In select expressions with a HAVING clause but
 without a GROUP BY clause, you cannot directly name columns in
 the select list or HAVING clause.  You can refer to them only as
 function arguments, or in a WHERE clause.

 User Action:  Either make the column named in the message a
 function argument, or if it is in a HAVING clause, change the
 HAVING clause to a WHERE clause.  In general, avoid using HAVING
 without GROUP BY.  Use WHERE instead.

 Column <text>.<text> cannot be UNIQUE because it can contain
 nulls.

 Explanation:  You specified a column using the UNIQUE
 constraint.  The column may contain nulls.  This is not legal
 because two rows cannot contain the NULL values in this column.

 User Action:  Define the named field as NOT NULL.

 Column <text> is not a list field

 Explanation:  The column specified in a SEGSTR.CREATE or
 SEGSTR.OPEN statement must be a list field.  This column is not.

 User Action:  Specify a column whose data type is list

 Column <text> is not included in the FOR UPDATE clause of cursor
 <text>

 Explanation:  The SQL interface to Rdb/VMS provides the FOR
 UPDATE clause on a cursor definition for DB2 compatablity.  The
 clause is entirely optional.  If a FOR UPDATE clause is
 specified on the cursor and an UPDATE statement that uses the
 CURRENT OF clause with that cursor changes a column which is not
 one of the columns included in the FOR UPDATE clause of the
 DECLARE CURSOR statement, you will get this warning message.

 User Action:  No action is required.  This message will not
 effect the execution of the statement.

 The column CHECK constraint cannot refer to the column <text>

 Explanation:  The CHECK constraint cannot refer to the column
 because the constraint is defined only for a column, not the
 entire table.

 User Action:  Refer to the only that column for which this CHECK
 constraint is being defined or define the CHECK constraint for
 the entire table.

 <text> in relation <text> will not be transferred

 Explanation:  You entered a SELECT FIELDS ALL clause in the
 CREATE TRANSFER statement to move a relation that contains a
 COMPUTED_BY field using a value expression that is unsupported.
 The CREATE TRANSFER statement is accepted with all the fields of
 this MOVE RELATION clause except the specified COMPUTED_BY field
 that is unsupported.

 User Action:  Refer to the CREATE TRANSFER statement in the Data
 Distributor Handbook for information on what value expressions
 are supported.

 Command line longer than <value> character maximum

 Explanation:  You typed a command line longer than the current
 maximum line length.

 User Action:  Break up the command line with continuation lines.
 There is no practical limit on the total length of all
 continuation lines in a single command.

 Constraint name <text> already exists in this schema

 Explanation:  You requested that a constraint be named with the
 name of an existing constraint.

 User Action:  Choose a different name.

 Constraint name <text> was not qualified and is in multiple
 schemas

 Explanation:  You must qualify the constraint name with an
 authorization identifier when accessing more than one schema
 that uses that constraint name.

 User Action:  Make sure the DECLARE SCHEMA statements include
 authorization identifiers and retype the query using the
 appropriate authorization identifier.

 Cannot begin program with continuation character

 Explanation:  Apparently the COBOL program starts with a
 continuation character.

 User Action:  Correct the source text and resubmit the job.

 Conflicting dictionary requirements

 Explanation:  You specified both the DICTIONARY IS REQUIRED and
 DICTIONARY IS NOT REQUIRED clause in the same ALTER SCHEMA
 statement.

 User Action:  Change the ALTER SCHEMA statement to include only
 one type of DICTIONARY REQUIRED option.

 Constraint <text> is not defined in schema

 Explanation:  The specified constraint does not exist in the
 current schema.

 User Action:  Declare the correct schema.  Check the constraint
 name for correct spelling.  Check the constraint definition to
 make sure you did not specify a term where the constraint name
 was expected.

 <text> is a constant host variable

 Explanation:  You referred to a host variable which was declared
 as a constant.  Constant declarations are not supported.

 User Action:  Either specify the constant as a literal, or use a
 host variable with that value.

 Conflicting READ ONLY Attributes

 Explanation:  You specified both READ ONLY and READ WRITE in an
 ALTER STORAGE AREA statement.

 User Action:   Re-enter the statement with either READ ONLY or
 READ WRITE, not both.

 Conflicting snapshot attributes

 Explanation:  The CREATE SCHEMA statement contained conflicting
 snapshot options.

 User Action:  Either remove the SNAPSHOT DISABLED clause from
 the root file  parameters, or remove the SNAPSHOT clause from
 the storage area       parameters.

 P characters must be contiguous in an edit string

 Explanation:  More than one P characters are permitted in an
 edit string, but they must all be contiguous.  This edit string
 contained more than one P characters that are not contiguous.

 User Action:  Make the P characters contiguous.

 The trigger actions on trigger <text> and trigger <text>
 conflict

 Explanation:  You cannot have two triggers which will be
 triggered for the      same event on the same table.  These two
 triggers would both    be triggered by the same event.

 User Action:  Combine the two triggers into a single trigger.

 Column qualifier <text> is already defined

 Explanation:  You either specified the same alias more than once
 in a select expression or did not specify an alias in a select
 expression that joins a table with itself.

 User Action:  Either use unique aliases or introduce an alias.

 Column qualifier <text> is not defined

 Explanation:  You qualified a column name with an alias or table
 not specified in the FROM clause of the select expression.

 User Action:  Make sure the qualifier you used matches an alias
 or table specified in the FROM clause.

 Correlated references in functions must not be in expressions

 Explanation:  You cannot use a correlated reference that is part
 of a value expression containing comparison operators, when the
 value expression is itself an argument to a function.  For
 example, SUM(corr_reference + 5).

 User Action:  Reformulate the select expression to avoid using a
 correlated reference in this manner.

 CREATE STORAGE AREA statement only valid as part of a CREATE
 SCHEMA statement

 Explanation:  The CREATE STORAGE AREA statement is only valid as
 part of the    CREATE SCHEMA statement.

 User Action:  Place the CREATE STORAGE statement in the CREATE
 SCHEMA statement.

 Error retrieving collating sequence <text>

 Explanation:  SQL could not retrieve the specified collating
 sequence; see the message that follows.

 User Action:  Correct the problem and try the operation again.

 <text> ignored due to setting of <text> logical name

 Explanation:  Either "USING CONTEXT" or "CONTEXT qualifier" will
 be named first.  In the precompiler and module language
 processor respectively, the named feature will be ignored
 because the logical name named in the message was defined as
 "TRUE".

 User Action:  If you want to migrate the application without the
 use of context items (i.e.  2PC/DDTM), no action is required.
 To use a distributed transaction, you must change the definition
 of the logical name to "FALSE" or deassign it.

 This statement not allowed in procedure in CONTEXT list

 Explanation:  A procedure that was mentioned in the
 /CONTEXT=(proc,proc) list contains a statement which may not
 receive a context parameter.

 User Action:  Remove the specified procedure name from the list.
 Using /CONTEXT=ALL is permitted, since those statements which
 may not receive a context parameter will not.

 Statement already declared as cursor <text>

 Explanation:  The statement id passed into a declare cursor
 procedure was already declared as the cursor named in the
 message.  Each statement can create only one cursor.

 User Action:  Declare another statement to create a unique
 statement id for each cursor.

 Cursor <text> was already open

 Explanation:  You opened a cursor that was already open.  An
 implicit close will be done on the cursor and the cursor
 reopened.

 User Action:  None.  This is just a warning.

 Cursor name <text> has already been declared

 Explanation:  You cannot use the same name in more than one
 DECLARE CURSOR statement.

 User Action:  Change the name of this cursor.

 Cursor <text> is not opened

 Explanation:  You named a cursor that was not open in a FETCH
 statement, CLOSE statement, or in the WHERE CURRENT OF clause of
 an UPDATE or DELETE statement.

 User Action:  Issue an OPEN statement for the cursor before
 naming it in any of those statements.  Close the cursor only
 once after opening it.

 CURRENT OF cursor-name is allowed only in DECLARE LIST CURSOR,
 UPDATE and DELETE statements

 Explanation:  The CURRENT OF cursor-name clause is used to
 modify or delete the current record in a cursor.  It has no
 meaning in the WHERE clause of a select expression except in
 declare list cursor.

 User Action:  Replace the WHERE CURRENT OF clause with a WHERE
 predicate clause that specifies the record you wish to select.

 CURRENT OF cursor-name is required

 Explanation:  In a positioned INSERT statement, the WHERE clause
 must be WHERE CURRENT OF cursor-name.

 User Action:  Restrict usage of to only WHERE CURRENT OF

 CURRENT OF clause cannot refer to cursor based on prepared
 statement

 Explanation:  The CURRENT OF clause of an UPDATE or DELETE
 statement specifies a cursor based on a prepared statement.
 Because the prepared statements are generated at run time, you
 cannot precompile UPDATE or DELETE statements that refer to
 cursors based on them.

 User Action:  Use a cursor which is based on an embedded SELECT
 statement (which is known at compile time), or dynamically
 execute the UPDATE or DELETE statement so it can be interpreted
 at run time.

 Cursor statements must be executed in the same transaction

 Explanation:  The statement was executed in the wrong
 transaction.  A cursor statement, such as FETCH, INSERT
 (positioned), UPDATE (positioned), DELETE (positioned), OPEN
 (list cursor) must be executed in the same transaction as the
 OPEN statement of the cursor to which the statement refers.

 User Action:  If a context structure was used for the OPEN
 statement, the same one must be used for the statements which
 operate on the cursor.  If no context structure was used for the
 OPEN statement, no context structure may be used for the
 statements which operate on the cursor.

 Cursor <text> has two open procedures

 Explanation:  There are two open procedures for this cursor.  A
 module can only have one procedure which opens a particular
 cursor.

 User Action:  Remove one of the procedures which opens this
 cursor.  Call the remaining procedure more than one time.

 USING clause not allowed for this cursor

 Explanation:  An OPEN or FETCH statement can specify a USING
 clause only for cursors based on a statement named in a PREPARE
 statement.  The cursor specified in this OPEN or FETCH statement
 is not.

 User Action:  Remove the USING clause from the OPEN or FETCH
 statement.

 Data conversion error

 Explanation:  An error occurred during data conversion.  Refer
 to next message.

 User Action:  The secondary message should clarify the problem.

 Date data type not supported in this context

 Explanation:  The output of a date value to the language file is
 not supported.

 User Action:  Do not use dates in this manner.

 Data type unknown.  Expression cannot use only host variables

 Explanation:  An assignment or a predicate must have at least
 one database field or literal.

 User Action:  You must use a database variable or literal in the
 expression.

 No DECLARE SCHEMA statement specified an identifier of <text>

 Explanation:  You specified an unknown authorization identifier
 to qualify a table or view name in a select expression.

 User Action:  Check the query and the DECLARE SCHEMA statement
 to make sure the authorization identifiers match.

 db handle should be specified for EXTRACTION ROLLUP transfers

 Explanation:  In a CREATE TRANSFER statement of an EXTRACTION
 ROLLUP transfer, you are attempting to move a relation without
 specifying the database handle of the source database.

 User Action:  Reenter the CREATE TRANSFER statement by
 specifying the database handle of the source database for each
 of the move-relation-clauses.

 Schema cannot be dropped because it is currently in use.

 Explanation:  You issued a DROP SCHEMA statement, but another
 user had declared the same schema.

 User Action:  Wait for other users to finish with the schema.
 If the schema is in use, however, one would question the wisdom
 of trying to delete it.  Remember that patience is a virtue.

 DBKEY reference is ambigous

 Explanation:  You made an unqualified reference to DBKEY in a
 context        where there is more than one source of a dbkey.

 User Action:  Add a table qualifier to the DBKEY reference.

 The DBKEY for table <text> is <value> bytes, host variable
 <text> must be the same size or larger.

 Explanation:  The host variable you are using with the DBKEY is
 not the        same size as the dbkey.

 User Action:  Allocate a host variable which is the correct
 size.

 The data dictionary pathname, <text>, chosen for the schema name
 already exists

 Explanation:  The data dictionary path name chosen for the
 schema name already exists in the current directory.

 User Action:  Use another, unique data dictionary path name.

 Handle already declared

 Explanation:  You declared a database handle via ACMS.  This
 interferes with defining a handle through the dynamic interface.

 User Action:  You should not specify another handle.

 Handle already declared

 Explanation:  You have declared a database handle via ACMS.
 This interferes with defining a handle through the dynamic
 interface.  This also interferes with declaring multiple
 database handles.

 User Action:  You should not specify another handle.

 The authorization identifier must be a longword

 Explanation:  Authorization identifiers that are passed from a
 program must be longwords passed by descriptor.

 User Action:  Define the authorization identifier to be a
 longword.  Examples:  For COBOL:  01 AUTHID PIC S9(9) COMP.  For
 FORTRAN:  INTEGER*4 AUTHID.

 Authorization identifier <text> is already part of this
 transaction

 Explanation:  You specified an authorization identifier twice
 within in the transaction parameters of SET TRANSACTION or
 DECLARE TRANSACTION.

 User Action:  Specify the authorization identifier only once.

 DECLARE TRANSACTION and DECLARE SCHEMA must be before executable
 statements

 Explanation:  DECLARE TRANSACTION and DECLARE SCHEMA must come
 before the first executable statement in a program.  An
 executable statement is a statement such as SELECT, INSERT,
 UPDATE, OR CREATE.  To avoid this error, put all DECLARE SCHEMA
 and DECLARE TRANSACTION statements in a context file, if
 possible.

 User Action:  Move all DECLARE TRANSACTION statements and
 DECLARE SCHEMA statements before all executable statements.  You
 should specify all DECLARE SCHEMA statements before the first
 DECLARE TRANSACTION statement.

 DECLARE SCHEMA must be before other DECLARE statements

 Explanation:  All DECLARE SCHEMA statements must come before any
 DECLARE CURSOR, DECLARE TRANSACTION, or DECLARE TABLE statements
 in a program.

 User Action:  Move all DECLARE SCHEMA statements before other
 DECLARE statements.

 VAX Data Distributor fatal error

 Explanation:  You entered a VAX Data Distributor statement that
 failed.

 User Action:  Refer to the explanation in the user action
 section of the secondary error message.

 Data Distributor ACK file format not understood

 Explanation:  The format of the ACK file was not as expected by
 SQL.

 User Action:  See the system manager to check for compatibility
 between versions of SQL and DDAL.  If not incompatible, submit
 SPR.

 Data Distributor not installed

 Explanation:  The VAX Data Distributor product is not installed
 on the system.

 User Action:  See the system manager to install the product.

 You referred to parameter <text> in a DDL statement

 Explanation:  You specified a parameter in a DDL statement such
 as a   CREATE VIEW or CREATE TRIGGER statement.  This is not
   supported.

 User Action:  Remove the parameter specification.

 Installed version of data dictionary does not support this SQL
 version.

 Explanation:  The version of the data dictionary on your system
 does not contain the necessary SQL support.

 User Action:  Upgrade the version of data dictionary on your
 system.  Alternatively, do not access the data dictionary with
 this version of SQL.

 DECLARE CURSOR statement cannot include an INTO clause

 Explanation:  You specified an INTO clause in the select
 expression in the DECLARE CURSOR statement.  It should go in the
 FETCH statement or in a singleton select statement.

 User Action:  Remove the INTO clause.

 Command line specified default constraint evaluation mode is off

 Explanation:  Your command line specified (either explicitly or
 by     default) that the constraint mode when you start a
      transaction is OFF; that is, that by default, constraints
 will not be evaluated until a COMMIT is executed.  The ANSI
    and ISO SQL standards require that the constraint mode when
 you start a transaction be ON; that is, that constraints be
    evaulated at the end of every SQL statement.

 User Action:  If it is important to have standard behavior in
 your program,  and you have constraints in your database, you
 should specify         the /CONSTRAINT_DEFAULT_MODE=ON in the
 module language command        line or
 /SQLOPTIONS=(CONSTRAINT_DEFAULT_MODE=ON) in the
        precompiler command line.

 A schema has already been declared with the default
 authorization identifier

 Explanation:  You attempted to declare a default schema when
 there already was a default schema.  In interactive SQL, you get
 this error only if you choose not to override the current
 default schema declaration.

 User Action:  Include an authorization identifier which has not
 been declared in the DECLARE SCHEMA statement.

 You specified a default value for <text> which is inconsistent
 with its data type

 Explanation:  The value specified for the default value must
   have the same type (i.e.  both character, both exact numeric,
 both approximate numeric or both dates) as the column or domain
 for which it is the default.  It must also be small enough to
  fit into column or domain.

 User Action:  Replace the specified value with a value that is
 compatible     with the column.

 Default values are not allowed for computed columns

 Explanation:  You specified a default value for a computed
 column,        for which defaults are not supported.

 User Action:  Remove the default clause from this definition.

 Default values are not supported for the data type of <text>

 Explanation:  You specified a default value for a data type
 (such as segmented     string) for which defaults are not
 supported.

 User Action:  Remove the default clause from this definition.

 Only one degree mode may be specified for a transaction

 Explanation:  You specified both concurrency options
 (CONSISTENCY LEVEL 2 and CONSISTENCY LEVEL 3) in a DECLARE
 TRANSACTION statement.

 User Action:  Specify only one option in your DECLARE
 TRANSACTION statement.

 EXPORT errors, interchange file deleted

 Explanation:  The export that you were performing could not be
 successfully completed.

 User Action:  Determine why the export failed and correct that
 situation.

 DELETE LIST cannot reference dynamic table cursor, <text>

 Explanation:  A precompiled DELETE LIST statement references a
 table cursor that is dynamic.

 User Action:  The DELETE LIST statement for the dynamic cursor
 should be PREPAREd and EXECUTEd.

 Implicit cascading may not be supported in a future version

 Explanation:  On a DROP TABLE, VAX SQL will currently drop all
 indexes, views         triggers and constraints which reference
 the table.  In a       future release, these objects will only
 be dropped if you      specify CASCADE.        On a DROP VIEW,
 VAX SQL will currently drop all views which    references that
 view.  In a future release, they will only be  dropped if you
 specify CASCADE.

 User Action:  If you want these objects to be deleted, specify
 the CASCADE    option on the drop.

 Deprecated Feature

 Explanation:  The syntax indicated is a deprecated feature.  It
 may not be     supported in a future version of VAX SQL.

 User Action:  Please look in the appendix of deprecated feature
 and    replace this feature with the feature that has superceded
 it.

 A dictionary definition used by schema <text> has changed

 Explanation:  This database refers to a definition in the
 dictionary that has changed.

 User Action:  Use the INTEGRATE statement to resolve any
 differences.

 Use the INTEGRATE statement to resolve any differences between
 the dictionary and the database

 Explanation:  The data definitions in the data dictionary no
 longer match the definitions in the database file.

 User Action:  Use the INTEGRATE statement to resolve any
 differences.

 Views and tables must be moved from the same schema

 Explanation:  The user entered a move tables clause specifying a
 schema with a different as the schema named in the move views
 clause.

 User Action:  Enter the CREATE TRANSFER statement with a move
 views clause whose schema is the same as the one in the move
 tables clause.

 more than 31 digits in a numeric edit string

 Explanation:  The edit string generates more than 31 digits.

 User Action:  Reduce the number of digits in this numeric
 picture string.

 Data Distributor DPB buffer not understood

 Explanation:  The format of the DPB buffer from the ACK file was
 not as expected by SQL.

 User Action:  See the system manager to check for compatibility
 between versions of SQL and DDAL.  If not incompatible, submit
 SPR.

 Index <text> is also being dropped.

 Explanation:  When you issue the DROP TABLE statement, SQL also
 drops all indexes that use that table.  This message notifies
 you which indices those are.  It is informational only.

 User Action:  None.

 VIA clause on storage map <text> is also being dropped.

 Explanation:  When you issue the DROP TABLE statement, SQL also
 drops the the index for that table.  In order to drop the index,
 any via clauses which reference the index must be delete so the
 index can be dropped.  The message is informational only.

 User Action:  None.

 Trigger <text> is also being dropped.

 Explanation:  When you issue the DROP TABLE statement, SQL also
 drops all triggers that use that table.  This message notifies
 you which triggers SQL is dropping.  The message is
 informational only.

 User Action:  None.

 View <text> is also being dropped.

 Explanation:  When you issue the DROP TABLE statement, SQL also
 drops all views that use that table.  This message notifies you
 which views those are.  It is informational only.

 User Action:  None.

 DROP SCHEMA statement is only supported with Rdb/VMS Version 3.0
 or later

 Explanation:  SQL will not drop        schemas without Version
 3.0 or later of Rdb/VMS        installed on the system.

 User Action:  Install Version 3.0 or later of Rdb/VMS on the
 system.        Alternatively, you can delete the schema by
 deleting       the files at DCL level and from the dictionary by
 using  the dictionary utility.

 Date or time format must be less than 999.

 Explanation:  You entered a DATE or TIME value greater than 999
 in the SET DATE FORMAT statement.

 User Action:  Enter a value less than or equal to 999.

 You can specify DATE or TIME only once each.

 Explanation:  You entered entered DATE date-number twice
       or TIME time-number twice in the SET DATE FORMAT
 statement.

 User Action:  Enter nothing, or enter DATE, TIME, or one of each
 with SET DATE FORMAT.

 field <text> has different definitions in relations <text> and
 <text>

 Explanation:  In a CREATE TRANSFER statement of an EXTRACTION
 ROLLUP transfer, you are attempting to move a field which does
 not have the same definition in all the source databases.  Since
 we cannot have two definitions of a field in the target
 database, the CREATE TRANSFER command is invalid.

 User Action:  Reenter the CREATE TRANSFER statement by including
 only one definition of the field mentioned above or by changing
 all the definitions of this field into the same type.

 <text> is a duplicate procedure name

 Explanation:  There are two procedures in this module with this
 name.

 User Action:  Change the name of one of the procedures.

 Duplicate <text> referential action

 Explanation:  You specified two update or two delete actions on
 a referential  constraint.  This is not supported.

 User Action:  Remove one of the referential actions.

 Variable <text> is already defined

 Explanation:  You defined a SQL variable for which there was
 already a declaration.

 User Action:  Either use the variable, or specify the name of a
 variable which is not already defined.

 Host variable <text> is an array whose bounds are determined at
 runtime

 Explanation:  The SQL precompilers do not support references to
 arrays whose bounds are determined at run time
 (dynamically-sized arrays).

 User Action:  Assign the value in the dynamically-sized array to
 a field which is not in a dynamically-sized array before using
 it in an SQL statement.

 Empty message vector returned.  Please submit an SPR

 Explanation:  The database system returned an empty message
 vector and nothing can be determined about the success or
 failure of the SQL statement for which the message vector was
 returned.  This is a database system software error.

 User Action:  Submit an SPR including the source of the program
 which caused this error.

 End of input

 Explanation:  No more input was given to SQL.

 User Action:  None.

 Host variable <text> is an enum variable which is illegal in SQL
 statements.

 Explanation:  The named variable is defined as a C enum
 variable.  Such fields are not legal in SQL statements.

 User Action:  Use a different variable.

 Error attaching to declared schema <text>

 Explanation:  A DECLARE SCHEMA statement specified an invalid or
 nonexistent file specification or data dictionary path name.
 See the messages following this message for more information.

 User Action:  Change the DECLARE SCHEMA statement to specify a
 valid file specification or path name.

 Could not use database file specified by SQL$DATABASE

 Explanation:  If you do not issue an explicit DECLARE SCHEMA
 statement, SQL uses the database file specified by the logical
 name SQL$DATABASE.  Because the logical name SQL$DATABASE is not
 defined or does not refer to a valid database, SQL could not
 attach to a database.  See the messages following this message
 for more information.

 User Action:  Explicitly declare a schema before executing any
 statements which require a database, or define the logical name
 SQL$DATABASE to specify the database file you wish to use.

 Error creating schema filename <text>

 Explanation:  There was an error creating the schema.

 User Action:  Correct CREATE SCHEMA statment and try again.

 An error was detected

 Explanation:  This is the exit status for a preprocessor when an
 error was detected.

 User Action:  Correct the error in the host language program and
 resubmit the job to the preprocessor.

 Error including record at pathname "<text>"

 Explanation:  An error was reported trying to include a record
 from the dictionary.

 User Action:  Correct the pathname in the include from
 dictionary statement.

 Error symbol deleted

 Explanation:  When parsing an SQL statement, the parser
 encountered an error.  The message for that error appeared prior
 to this message.  In an attempt to recover from that error SQL
 deleted the token it found, and generated this message to help
 you understand any additional messages that follow.

 User Action:  None.  This is an informational message only.

 Error symbol replaced by <text>

 Explanation:  When parsing an SQL statement, the parser
 encountered an error.  The message for that error appeared prior
 to this message.  In an attempt to recover from that error, SQL
 replaced the token it found with the specified token, and
 generated this message to help you understand any additional
 messages that follow.

 User Action:  None.  This is an informational message only.

 repeat count in edit string is not numeric

 Explanation:  The user specified an edit string that contained a
 repeat count that was not a number, for example, X(9) is legal,
 but X(a) is not.

 User Action:  Specify only numeric values for repeat counts.

 EVALUATING clause ignored

 Explanation:  The DECLARE TRANSACTION statement in SQL does not
 support the EVALUATING clause to specify when the database
 system evaluates constraints.  Constraints are evaluated as
 specified in their definitions.

 User Action:  Issue the DECLARE TRANSACTION statement without
 the EVALUATING clause.

 Attempted to EXECUTE a SELECT statement

 Explanation:  You used a prepared SELECT statement in an EXECUTE
 statement.  In dynamic SQL, the only way to process prepared
 SELECT statements is through cursors.

 User Action:  Define a cursor based on the statement you tried
 to execute, and use the cursor in OPEN and FETCH statements.
 Otherwise, use non-SELECT statements only in EXECUTE statements.

 Expected a numeric literal

 Explanation:  A numeric literal was expected in this context.

 User Action:  Correct the syntax.

 A query expression was expected

 Explanation:  SQL expected a query expression.  You entered
 something else.

 User Action:  Enter a query expression.

 Exporting a data dictionary with NODATA is not allowed

 Explanation:  You used the NODATA option when exporting a
 dictionary database.

 User Action:  You cannot use the NODATA option when exporting
 data dictionaries.  The data dictionary cannot use the resulting
 database.  Use the DATA option and try again.

 Exporting a data dictionary with NOEXTENSIONS is not allowed

 Explanation:  You used the NOEXTENSIONS option when exporting a
 dictionary database.

 User Action:  You cannot use the NOEXTENSIONS option when
 exporting data dictionaries.  The data dictionary cannot use the
 resulting database.  Use the EXTENSIONS option and try again.

 unexpected data at the end of the .RBR file

 Explanation:  Internal error - found more data than expected in
 the Rdb/VMS interchange file (.RBR).

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.

 Only one schema allowed by EXTRACTION and REPLICATION transfers

 Explanation:  You have specified tables to be moved which come
 from more than one schema.

 User Action:  Use multiple transfers to move tables from
 multiple schemas.

 A fetch has not been done yet for cursor <text>

 Explanation:  You named a cursor in a CURRENT OF clause of an
 UPDATE or DELETE statement but you did not issue a FETCH
 statement for that cursor.

 User Action:  Issue a FETCH statement for the cursor.

 Domain <text> already exists in this schema

 Explanation:  You requested that a domain be named with the name
 of an existing type.

 User Action:  Choose a different name.

 Computed column may not reference a foreign key

 Explanation:  You specified a foreign key constraint for a
 computed       column, which does not support this constraint.

 User Action:  Remove the foreign key constraint from this
 definition.

 Column <text> is not unique in tables in the FROM clause

 Explanation:  The specified column exists in more than one of
 the tables specified in the FROM clause.

 User Action:  Qualify the column name in the select list with
 the table name or an alias.

 global field <text> not defined as specified

 Explanation:  The base field for a local field is not defined.

 User Action:  This is caused by an inconsistency in the
 database.  Try to recover the missing global field.

 Column <text> was not found in the tables in current scope

 Explanation:  The specified column does not exist in the tables
 specified in the current scope.

 User Action:  Check the select expression:  you may have
 mistyped the column name or specified the wrong table name or
 alias to qualify the column name.

 Column <text> is not defined in table <text>

 Explanation:  The specified column does not exist in the table
 specified.

 User Action:  Check the select expression:  you may have
 mistyped the column name or specified the wrong table name or
 alias to qualify the column name.

 <text> is not a column in table, <text>

 Explanation:  The column you specified is not part of the named
 table.

 User Action:  Check the table definition for the correct column
 name or specify another table.

 Indirect command file buffer flushed for Control C

 Explanation:  You typed Control-C while executing an indirect
 command file.

 User Action:  None.

 Column <text> in table <text> does not match assumed <text> data
 type

 Explanation:  You implicitly declared the named column with
 numeric, character or date data type when using it in a forward
 reference.  When the named table was eventually created, the
 actual column declaration did not match the implicit one.

 User Action:  Change the forward declaration or the column
 declaration so that the two have the same basic data type.

 Column <text> in table <text> does not match <text> of forward
 reference

 Explanation:  You implicitly declared the named column when
 using it in a forward reference.  When the named table was
 eventually created, the actual column declaration did not match
 the implicit one.

 User Action:  Change the forward declaration or the column
 declaration so that the two match in data type, length and
 scale.

 Column <text> in forward reference of table <text> not declared

 Explanation:  You implicitly declared the named column when
 using it in a forward reference.  When the named table was
 eventually created, the column was not declared.

 User Action:  Change the forward declaration or the actual table
 declaration so that the table contains all of the columns found
 in the forward declaration.

 Host variable <text> is an unsupported passed-length variable

 Explanation:  The host variable declaration uses the FORTRAN
 passed-length (*) feature which is not supported.

 User Action:  Either change the declaration so that only
 supported attributes are used, or move the data to another
 variable which uses only supported attributes.

 Forward referenced table <text> not declared

 Explanation:  You used the named table in a forward reference.
 This table was never created.

 User Action:  Change the CREATE SCHEMA statement to include the
 definition of all forward declared tables.

 Host variable <text> is function which is illegal in SQL
 statements.

 Explanation:  The named variable is defined as a C function.
 Functions refnereces are not supported in SQL statements.

 User Action:  Use a different variable.

 interchange file is corrupt

 Explanation:  Internal error - probably mismatched BEGIN and END
 clumps.

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.

 Attempt to get from a created list

 Explanation:  You attempted to do a SEGSTR.GET using a handle
 returned by a SEGSTR.CREATE statement.  You can only do
 SEGSTR.PUTs using the handle returned by create.

 User Action:  Specify the correct handle

 <text> does not support G_FLOAT

 Explanation:  /G_FLOAT was specified for a language such as
 COBOL which does not support the G_FLOAT data type.

 User Action:  Unless you are taking the G_FLOAT number and
 passing it to a language which understands G floating numbers,
 you probably want to reprecompile without the /G_FLOAT
 qualifier.  If you use it from this language, the compiled code
 will think it is a different number than the database system
 did.

 A hexadecimal string must have an even number of digits

 Explanation:  A hexadecimal string must have an even number of
 digits.  This is because it takes two hexadecimal digits to
 represent each ASCII character.

 User Action:  Enter a hexadecimal number with an even number of
 digits.

 Increasing the scale of column <text> may result in the loss of
 high order digits

 Explanation:  Changing the data type and/or increasing the scale
 of a   column may result in the loss of significant digits of
  the data already stored in that column.

 User Action:  None.  This is a warning message only.

 Host variable <text> was not declared

 Explanation:  Every host variable that is used in an SQL
 statement in a program must been declared in the host language.

 User Action:  Declare the specified variable using a supported
 declaration.

 Host variable, <text>, not within scope of BEGIN DECLARE and END
 DECLARE section

 Explanation:  Your program referred to a variable that was
 declared outside of the BEGIN DECLARE and END DECLARE
 statements.

 User Action:  Either move the desired host variable declaration
 to be within this section or remove the BEGIN DECLARE and END
 DECLARE statement.  You can also ignore this warning message.
 BEGIN DECLARE and END DECLARE are only for standard complicance.

 an authorization ID or a filename is required to create a schema

 Explanation:  The user specified an IMPORT or a CREATE SCHEMA
 statement without specifying an authorization ID or a filename.
 One of is required.

 User Action:  Specify the missing parameter and try the
 operation again.

 file <text> is corrupt or not an Rdb interchange file

 Explanation:  SQL IMPORT can recreate databases only from the
 Rdb/VMS interchange file (.RBR).  This file is not an Rdb/VMS
 interchange file (.RBR).

 User Action:  Try the operation again with the correct file
 name.

 Illegal character detected

 Explanation:  An illegal character has been detected.

 User Action:  Use only valid characters.

 An invalid SQLLEN(<value>) was found for a date field in the
 SQLDA

 Explanation:  You passed in a date column in a SQLDA with a
 SQLLEN that was not 8.

 User Action:  Set the SQLLEN to 8 for date columns in the
 SQLVAR.

 Illegal EXECUTE IMMEDIATE statement type

 Explanation:  You tried to issue a statement that is not allowed
 in an EXECUTE IMMEDIATE statement (SELECT, DECLARE, OPEN, FETCH,
 CLOSE, PREPARE, DESCRIBE, EXECUTE, INCLUDE, or WHENEVER).

 User Action:  Use PREPARE and a full EXECUTE statement for these
 statements.

 An invalid SQLLEN(<value>) was found for a FLOAT field in the
 SQLDA

 Explanation:  You passed in an SQLDA with a SQLTYPE FLOAT SQLLEN
 that was invalid.  Only 4, 8, an 16 are legal floating-point
 lengths.

 User Action:  Set the SQLLEN to 4, 8, or 16, depending on the
 length of the floating-point variable passed.

 Data dictionary definitions may not be included using FROM
 within CREATE SCHEMA

 Explanation:  You cannot use the FROM PATHNAME clause within a
 CREATE SCHEMA statement.

 User Action:  Create the schema first, then include the
 definitions.

 Illegal hexadecimal number.

 Explanation:  The format of a hexadecimal number is X'ffff',
 where ffff may be up to 16 hexadecimal digits.  A hexadecimal
 digit is a numeric digit (0 to 9) or an A, B, C, D, E, or F.
 The letters may be upper or lower case.  There must be an even
 number of digits.

 User Action:  Enter a proper hexadecimal number.  Make sure that
 the trailing apostrophe is included.

 An invalid SQLLEN(<value>) was found for a integer column in the
 SQLDA

 Explanation:  You passed in an integer column in a SQLDA with a
 SQLLEN that was invalid.  For SQLTYPE of INTEGER, SQLLEN must be
 4.  For SQLTYPE of SMALLINT, SQLLEN must be 2.

 User Action:  Set the SQLLEN to 2 for SMALLINT, or 4 for
 INTEGER.

 illegal character <text> in edit string

 Explanation:  An edit string contained the illegal character
 specified in the message.

 User Action:  Change the edit string to not have that character.

 Illegal string continuation

 Explanation:  Your program has illegal string continuation.

 User Action:  In COBOL, to continue a string you must do three
 things:  1) not end the string with a quote on the initial line;
 2) insert a continuation character (-) in the first column of
 the next line; and, 3) start the continued string with a quote
 as the first nonblank character after the continuation character
 (this quote is ignored).

 Host variable <text> is defined with an implicit dimension.

 Explanation:  The named variable is defined using the C feature
 of determining the dimension of an array from its
 initialization.  Such variables are not legal in SQL statements.

 User Action:  Define the array variable using an
 explicitly-sized array.

 Importing a data dictionary with NODATA is not allowed

 Explanation:  You used the NODATA option when importing a
 dictionary database.

 User Action:  You cannot use the NODATA option when importing
 data dictionaries.  The data dictionary cannot use the resulting
 database.  Use the DATA option and try again.

 index <text> not created - check spelling of the table name

 Explanation:  IMPORT could not process a CREATE INDEX clause
 because the named table was not defined in the schema.

 User Action:  Check that you spelled the table name correctly.

 index <text> not dropped - check spelling of the index name

 Explanation:  IMPORT could not process a DROP INDEX clause
 because the named index was not defined in the schema.

 User Action:  Check that you spelled the index name correctly.

 DEFINE and DELETE INDEX <text> specified

 Explanation:  The user specified a DEFINE and DELETE INDEX using
 the same name.

 User Action:  Specify a either a DEFINE or a DELETE INDEX.

 DEFINE INDEX <text> specified twice

 Explanation:  The user specified a DEFINE INDEX twice using the
 same name.

 User Action:  Specify a INDEX name only once.

 storage area <text> not dropped - check spelling of the storage
 area name

 Explanation:  IMPORT could not process a DROP STORAGE AREA
 clause because the named storage area was not defined in the
 schema.

 User Action:  Check that you spelled the storage area name
 correctly.

 storage map <text> not created - check spelling of the table
 name

 Explanation:  IMPORT could not process a CREATE STORAGE MAP
 clause because the named table was not defined in the schema.

 User Action:  Check that you spelled the table name correctly.

 storage map <text> not dropped - check spelling of the storage
 map name

 Explanation:  IMPORT could not process a DROP STORAGE MAP clause
 because the named storage map was not defined in the schema.

 User Action:  Check that you spelled the storage map name
 correctly.

 DEFINE and DELETE STORAGE AREA <text> specified

 Explanation:  The user specified a DEFINE and DELETE STORAGE
 AREA using the same name.

 User Action:  Specify a either a DEFINE or a DELETE STORAGE
 AREA.

 DEFINE and DELETE STORAGE MAP <text> specified

 Explanation:  The user specified a DEFINE and DELETE STORAGE MAP
 using the same name.

 User Action:  Specify a either a DEFINE or a DELETE STORAGE
 AREA.

 DEFINE STORAGE MAP <text> specified twice

 Explanation:  The user specified a DEFINE STORAGE MAP twice
 using the same name.

 User Action:  Specify a STORAGE MAP name only once.

 DEFINE STORAGE AREA <text> specified twice

 Explanation:  The user specified a DEFINE STORAGE AREA twice
 using the same name.

 User Action:  Specify a STORAGE AREA name only once.

 Starting <text> definition <text>

 Explanation:  Importing Relation/Index/Constraint info message.

 User Action:  None.

 Completed <text>.  DIO = <value>, CPU = <text>, FAULTS = <value>

 Explanation:  Text for Import Tracing.

 User Action:  N/A.

 <text> is not a dictionary record definition

 Explanation:  The data dictionary path name in an INCLUDE FROM
 DICTIONARY statement must specify a dictionary record
 definition.  The dictionary object specified is not a record
 definition.

 User Action:  Change the path name to the path name for a record
 definition, or remove the INCLUDE statement.

 Altering column <text> to an incompatible data type may cause
 data loss

 Explanation:  Altering a column to a data type that is
 incompatible with the  old data type might cause data already
 stored in that column  to appear lost.

 User Action:  None.  This is a warning message only.

 There is another index named, <text>, in this schema

 Explanation:  The index name you tried to define already exists.

 User Action:  Try another index name.

 Indicator variable <text> is not an unscaled fixed numeric

 Explanation:  You must declare indicator variables as the host
 language equivalent of an unscaled integer data type.

 User Action:  Declare the indicator variable as an unscaled
 integer host variable.

 Index <text> is not defined in schema

 Explanation:  The specified index does not exist in the current
 schema.

 User Action:  Declare the proper schema.  Spell the index name
 correctly.  You may have specified an expression where an index
 name was expected.

 Indicator variable <text> is not a SMALLINT

 Explanation:  Indicator variables in the dynamic interface
 should be declared as the host language equivalent a SMALLINT
 data type.

 User Action:  In COBOL, declare indicator variables as PIC S9(4)
 COMP.  In FORTRAN, declare indicator variables as INTEGER*2.  In
 PL/I, declare indicator variables as FIXED(15) BINARY.

 Index <text> already exists in this schema

 Explanation:  You attempted to create an index with the name of
 an existing index

 User Action:  In the precompiler and module language, this is
 just a warning.  If the index exists when you execute the
 statement, you will get a fatal error.  If you expect to drop
 the index before you execute this statement, then you do not
 need to make any changes.  In interactive, dynamic and runtime
 for precompiled and module language programs, this is a fatal
 error.  You must choose a different name.

 An informational was detected

 Explanation:  This is the exit status for a preprocessor when an
 informational was detected.

 User Action:  Correct the error in the host language program and
 resubmit the job to the preprocessor or ignore the
 informational.

 Error reading input file

 Explanation:  There was an error reading from the module
 language or precompiler source file.  SQL will display a
 secondary status message.

 User Action:  Act upon the secondary status message.  See the
 system manager, if necessary.

 Column <text> appears more than once in the INSERT column list

 Explanation:  You specified the same column name more than once
 in an INSERT statement.  Columns can only appear once.

 User Action:  Remove one occurrence of all columns which appear
 more than once.

 List cursor <text> cannot insert into READ ONLY table cursor
 <text>

 Explanation:  The list cursor named is an INSERT ONLY cursor
 while the table cursor that it references is a READ ONLY cursor.

 User Action:  The table cursor that the list cursor is based on
 must either be an INSERT ONLY or UPDATE cursor.  Jump that error
 message base into the next available range for the client.

 List cursor <text> cannot fetch from INSERT ONLY table cursor
 <text>

 Explanation:  The list cursor named is a READ ONLY cursor, but
 the table cursor is an INSERT CURSOR which won't allow FETCHes.

 User Action:  The list cursor must be an INSERT ONLY list cursor
 or the table cursor must be an INSERT or UPDATE cursor.

 Interval option ignored for system relation area

 Explanation:  The storage area that contain the system relations
 must   have UNIFORM page formats.  Either through the use of the
 defaults, or by directly specifing the INTERVAL option,
        SQL has been told to apply the INTERVAL option for the
 area   containing the system relations.  SQL is ignoring that
  option.

 User Action:  Nothing.  This is an informational message.  The
 user might     want to change the command if it originated in a
 command        file.  This may avoid confusion later.

 Interval option not valid for system relation area

 Explanation:  The storage area for RDB$SYSTEM was defined to
 have the       interval option.  This is not allowed for
 RDB$SYSTEM.

 User Action:  Remove the interval option from the command and
 try again.

 INTO clause is not allowed in this context

 Explanation:  The INTO clause may only be used for a single
 table or view.  It may not be used with a wildcard table or view
 specifiction.

 User Action:  Reenter the CREATE TRANSFER statement without
 specifying an INTO clause or name the tables and views
 individually, each with its own INTO clause.

 The table name specified in the INTO clause must not be
 qualified

 Explanation:  The user entered INTO xxx.yyy for an extraction
 rollup transfer.

 User Action:  Re-enter the statement without the 'xxx.'

 Interval value must be at least 256

 Explanation:  The specified interval value for space management
 pages is       too small.  The minimum value is 256 pages.

 User Action:  Change the interval value for space management
 pages on the   CREATE SCHEMA statement to a legal value.

 Interval value overwritten to 256 pages

 Explanation:  The specified interval value for space management
 pages is       too small.  The minimum value is 256 pages.  SQL
 overwrote      the specified value with 256.

 User Action:  Change the interval value for space management
 pages on the   CREATE SCHEMA statement to a legal value.

 Invalid Access Control List entry

 Explanation:  The syntax of the access control list entry string
 is not valid.

 User Action:  Correct the syntax of the access control list
 entry.

 Host variable <text> defined with illegal use of subscripts

 Explanation:  The named host variable uses subscripts in a way
 that is illegal for the C compiler.  Most likely the use is
 through a typedef that is defined as an array.

 User Action:  Use a different variable or redefine the type
 structure of the program.

 Invalid attribute value.  "<text>" attribute has an invalid
 value

 Explanation:  You specified an attribute with an invalid value.

 User Action:  Change the offending value and try the statement
 again.

 Invalid character in input

 Explanation:  The input contains an illegal or unrecognizable
 character.

 User Action:  Correct the source text and resubmit the job.

 Invalid character in numeric string

 Explanation:  The string appears to be a numeric literal.
 However, it contains one or more illegal characters.

 User Action:  Correct the source text and resubmit the job.

 column list in view definition contains the wrong number of
 names

 Explanation:  The list of column names you specified in a view
 definition contained a different number of names than the number
 of value expressions in the select list of the definition's
 SELECT expression.  There must be a strict one-to-one
 correspondence between the two lists.

 User Action:  Specify the same number of column names in the
 column list as value expressions in the select list.

 Column names must be qualified by table names.

 Explanation:  You must qualify the column name in a COMMENT ON
 COLUMN statement with a table name.

 User Action:  Specify the column name as
 <table-name>.<column-name>.

 Invalid command line

 Explanation:  You specified extra parameters or invalid command
 line syntax in a module language compiler command line.

 User Action:  Specify only supported command line options.

 unable to import constraint <text>

 Explanation:  Internal error - the named constraint will not
 appear in the recreated database.

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.  In the meantime,
 you can redefine this constraint explicitly.

 Invalid select list in a UNION CORRESPONDING query

 Explanation:  There are 2 columns with the same name in one of
 the    select lists in the UNION CORRESPONDING query expression.
 You cannot specify a column in the other select list with
      that name as well.

 User Action:  Either remove one of the columns with the same
 name from the  select list, or match columns to be combined in
 the UNION      by position rather than name.

 Invalid conversion between DATE column <text> and host variable
 <text>

 Explanation:  Only binary dates can be compared or assigned to
 or from DATE columns.

 User Action:  Use a date declaration for the host variable to be
 used with the date field:  in COBOL, use S9(11)V9(7) COMP; in
 PL/I, use CHAR(8) or BYTE_FIELD(8); in FORTRAN, use CHARACTER*8.

 Invalid DBKEY reference

 Explanation:  You can refer to dbkeys only on the right hand
 side of an     assignment or in an equals Boolean.

 User Action:  Remove the invalid dbkey reference.

 Invalid DISTINCT expression

 Explanation:  In a function specification, if DISTINCT is
 specified, the value expression must be just a column name.  You
 specified a value expression other than a column name in a
 function with the DISTINCT clause, such as SUM(DISTINCT
 SALARY_AMOUNT * .10).

 User Action:  Change the value expression to a column name or
 remove the DISTINCT clause.

 Invalid escape clause value

 Explanation:  The value specified in the escape clause of a LIKE
 predicate      must be a single character string value.

 User Action:  Specify a valid value expression in the escape
 clause

 unable to import field <text>

 Explanation:  Internal error - the named field will not appear
 in the recreated database.

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.

 Invalid function reference

 Explanation:  You cannot include in the WHERE clause (or in any
 subqueries of the WHERE clause) functions that use columns of
 tables in the FROM clause as their argument.

 User Action:  Change your select expression to eliminate
 functions with this type of argument.

 Host variable <text> was invalidly declared.

 Explanation:  Every host variable that is used in an SQL
 statement in a program must be declared in the host language
 using the supported subset of declaration syntax for the
 language.  Not using the supported subset causes this error.
 Another way this message can be generated is to use an indicator
 variable that is not a signed word (for example, in COBOL:  PIC
 S9(4) COMP).

 User Action:  Use host variable declaration syntax for this
 variable that is supported by SQL.

 unable to import index <text>

 Explanation:  Internal error - the named index will not appear
 in the recreated database.

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.  In the meantime,
 you can recreate this index explicitly.

 Only a numeric variable may be used receive the length

 Explanation:  You used a variable which was not numeric.  This
 is not supported.

 User Action:  Either omit the argument to receive the length, or
 use a numeric

 Invalid node size parameter specified

 Explanation:  You specified an invalid node size.  It was either
 less than or equal to zero or greater than 32768.

 User Action:  Review the command and specify a node size within
 the above range (but big enough to meet the implementation
 requirements).

 <text> is an invalid numeric literal

 Explanation:  An invalid numeric literal was specified which
 could not be converted to a numeric value.  This is usually
 because it is to big to fit into any VAX data type without
 losing significance.

 User Action:  Change the literal to be a valid numeric literal.

 Invalid numeric string precision (<value>), maximum precision is
 (<value>)

 Explanation:  You specified a precision for a NUMERIC, UNSIGNED
 NUMERIC, or DECIMAL field that exceeded the maximum.

 User Action:  Specify a precision that is less than the maximum.

 Invalid object file <text> specified

 Explanation:  SQL uses the same directory specification and file
 name for any files it creates (such as the language files) as
 that specified in the /OBJECT qualifier on the command line.
 You specified a nonexistent or invalid file specification
       for the /OBJECT qualifier.

 User Action:  Use a valid object file specification with the
 /OBJECT qualifier.

 ORDER BY number is less than 1 or exceeds count of select-list
 items

 Explanation:  The number in the ORDER BY clause, used to specify
 which expression from the select list to sort by, is bigger than
 the number of items in the select list or it is below 1.

 User Action:  Use a number which corresponds to an item in the
 sort list.

 Invalid percent fill parameter specified

 Explanation:  You specified an invalid percent fill parameter.
 It was either less than or equal to zero or greater than 100.

 User Action:  Review the command and specify a percent fill
 parameter within the above range.

 Invalid privilege for this object

 Explanation:  You used the ENTRY keyword with the GRANT
 statement.  ENTRY is supported for REVOKE only.  Or, a GRANT or
 REVOKE statement specified for a schema a privilege which is
 valid only for tables, or specified for a table a privilege
 which is valid only for a schema.

 User Action:  Do not use ENTRY with GRANT.  Or, make sure that
 the privileges you specify in GRANT or REVOKE are valid for the
 object (schema or table) named.

 Invalid privilege names specified in message file

 Explanation:  The names specified in PRIV_NAMES0 and
 PRINV_NAMES1 are incorrect.

 User Action:  Submit an SPR or contact your support center.

 Invalid qualifier <text> specified on command line

 Explanation:  You specified invalid command qualifiers in a
 module language compiler command line.

 User Action:  Specify only supported command line qualifiers

 Invalid referencing clause

 Explanation:  You specified a referencing clause on a trigger
 which is not   for update.  The referencing clause is only valid
 if the trigger         is invoked on updates.

 User Action:  Remove the referencing clause.

 unable to import table or view <text>

 Explanation:  Internal error - the named relation or view (and
 its data) has been lost.

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.

 Invalid range.  You specified <text>.  Valid range is from
 <value> to <value>

 Explanation:  You specified a value that was out of range.

 User Action:  Use a number that is in the specified range.

 Value for a list segment must be either a parameter or literal
 string

 Explanation:  The value for a list segment was something other
 than a literal string or a parameter.

 User Action:  Replace the value with one of the two valid
 parameters types.

 Select list cannot mix columns and functions without GROUP BY

 Explanation:  The select list in a select expression without a
 GROUP BY clause cannot include both functions and column
 references which are not in functions.

 User Action:  Either add a GROUP BY clause, remove the function
 references, or remove the column references that are not in
 functions.

 * is not allowed in this context

 Explanation:  You specified a column wildcard (* or p.*) in a
 context where wildcards are not supported, such as outside a
 select list or in a select list for a select expression
 containing a HAVING clause but no GROUP BY (in such a case, you
 cannot specify columns, either, unless they are an argument to a
 function).

 User Action:  Replace the wildcard with the column name you want
 to use.

 SQLCODE has an invalid data type

 Explanation:  SQLCODE must be declared as a signed longword.
 The declaration of SQLCODE in this program is a different data
 type.

 User Action:  Change the data type of SQLCODE.

 Invalid conversion for list column <text>

 Explanation:  You attempted to do an assignment using a list.

 User Action:  Do not use lists.

 Invalid segmented string handle

 Explanation:  The host variable supplied to hold a segmented
 string handle must be at least 4 bytes long.

 User Action:  Specify a larger host variable.

 Host variable <text> is defined as CHAR[1] and cannot be used in
 SQL statements.

 Explanation:  The named variable is defined as CHAR[1].  The
 length of character variables used in SQL statements must be at
 least 2 since SQL always includes a NULL terminator.

 User Action:  Use a different variable.

 Unable to IMPORT trigger <text>

 Explanation:  This is an internal error.  The named trigger will
 not appear in the recreated database.

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.  In the meantime,
 you can redefine this trigger explicitly.

 Invalid triggered statement

 Explanation:  You specified a statement or clause in a triggered
 statement      list which is not supported.  Examples of such
 statements are:         -      any statement other than DELETE,
 INSERT, UPDATE,                ROLLBACK or error statement.
 - a WHERE CURRENT OF clause in an UPDATE or DELETE
         statement.      -      a RETURNING clause on an INSERT
 statement.

 User Action:  Remove the invalid statement or clause

 Host variable <text> is based on an invalid type

 Explanation:  The host variable you referred to is based on a
 type which is either not a supported type definition or was
 invalidally declared.

 User Action:  Use a different type defintion.

 The value list must have as many items as the column list

 Explanation:  An INSERT statement must have as many values in
 the value list as there are in the column list.  You specified
 the wrong number of items.  Note that if there are any host
 structures in the value list, they will be expanded to include
 their elementary items.  In that case, to get the number of
 items in the value list, you must count the elementary items for
 all the host variables.

 User Action:  Enter the correct number of values.

 an unexpected I/O error occurred

 Explanation:  Unable to read any more of the Rdb/VMS interchange
 file (.RBR); part of the database may be imported.

 User Action:  Correct the problem indicated by the message that
 follows this message and try the operation again.

 Interactive SQL does not support the INTO clause in SELECT or
 FETCH

 Explanation:  SELECT and FETCH statements in interactive SQL
 cannot include INTO clauses, since interactive SQL does not
 support host variables.

 User Action:  Enter the statement again, without the INTO
 clause, to display the values on the terminal.

 Extraneous characters found after the end of the statement

 Explanation:  You typed extra characters after the end of the
 statement.

 User Action:  Check statement syntax for correct statement
 termination.

 Nonstandard -- You used a keyword as an identifier

 Explanation:  You specified an SQL keyword in a place where it
 is not         a valid keyword, but where an identifier may be
 specified.     The keyword will be used as an identifier.

 User Action:  None, this is an informational message.  However,
 note that      you will not be able to specify this identifier
 in any context         where the keyword may appear.

 <text> is the language file extension, please use another
 extension

 Explanation:  The input file type you specified to the
 precompiler is the same file type as the output file type.

 User Action:  Rename the file with the default file
 specifications and run the precompiler again.  Refer to the
 default file specifications in the Guide to Using SQL.

 Value not allowed on the language qualifier

 Explanation:  The SQL precompiler requires a language qualifier
 (such as /COBOL) to specify the host language.  However, you
 specified a value with that qualifier (such as COBOL=3), which
 is not allowed.

 User Action:  Remove the value from the language qualifier.

 <text> does not pass the data type for parameter <text> by
 descriptor

 Explanation:  The language specified in the LANGUAGE clause of
 the module will not support the data type specified for this
 parameter by descriptor.  However, you can build a descriptor as
 a record and pass the descriptor.  Hence, this is only a
 warning.

 User Action:  If you did not intend to pass the data type by
 descriptor, change the passing mechanism in the SQL module and
 in the host language.

 <text> does not support the data type for parameter <text>

 Explanation:  The language specified in the LANGUAGE clause of
 the module does not support the data type specified for this
 parameter.

 User Action:  If you did not intend to use a data type the
 language does not support, change the data type to one the
 language supports.  If you know the language does not support
 the data type, you can use it anyway.  This is is only a warning
 message.

 Truncating right hand side string for assignment to column
 <text>

 Explanation:  You executed an INSERT or UPDATE statement, and
 the string you assigned to a text column is longer than the
 column's definition.

 User Action:  The message is just a warning.  You can issue an
 UPDATE statement to change the value stored or a ROLLBACK
 statement to terminate the transaction and cancel the INSERT
 operation.

 LIMIT TO must specify an unscaled fixed numeric

 Explanation:  The "n" in LIMIT TO n ROWS must be a literal,
 parameter or host variable of an unscaled fixed numeric data
 type.

 User Action:  Change the LIMIT TO clause to use an unscaled
 fixed numeric data type for the row limit, n.

 Input line was too long

 Explanation:  The module language or procompiler source file
 contained a line which was too long for the input buffer.

 User Action:  Split the offending line into two or more
 different lines.

 List data type is not valid for parameter or variable

 Explanation:  It is illegal to define a parameter or variable
 with a data type of list

 User Action:  Use another data type.

 Truncation of a numeric value at compiletime

 Explanation:  SQL encountered an error trying to convert a
 numeric literal in the precompiler or module compiler to the
 data type of the field it was used with.

 User Action:  Change either the literal or field so that the
 literal can be assigned to the field

 Syntax error, looking for <text>, found <text> instead

 Explanation:  The syntax expected a specific keyword, but you
 entered another.

 User Action:  Check the syntax and reenter the correct keyword.

 <text>

 Explanation:  This message lists syntactically legitimate
 alternatives.

 User Action:  Consider options from the list.

 found <text> instead

 Explanation:  Last of three messages generated by syntax errors,
 this message shows the invalid syntax that SQL encountered.

 User Action:  Reenter the statement, or use EDIT to correct it.

 Syntax error, looking for a valid SQL statement, found <text>
 instead

 Explanation:  SQL did not find the beginning of a statement
 where it expected one.

 User Action:  Supply a valid statement.

 Syntax error, looking for:

 Explanation:  The syntax expected one of several valid
 possibilities, list follows.

 User Action:  Consider options from the list in the next
 message.

 Syntax error, looking for <text>, found <text> instead

 Explanation:  This is issued with a SQL-F-BUGCHK because it
 indicates that a severe error has occurred in the syntax tables.

 User Action:  Record the exact command line as typed, (use EDIT
 to write it to a file) and submit an SPR.  Then consider finding
 a workaround.

 Reducing the scale of column <text> may result in the loss low
 order precision

 Explanation:  Altering the scale of a column may result in the
 perceived loss         of data stored in that column due to
 rounding.

 User Action:  None.  This is a warning message.

 Cursor statment has active list cursor statements

 Explanation:  You executed a RELEASE statement on a a cursor
 statement while list cursors defined based on that cursor exist.

 User Action:  Release all of the list cursor statements before
 executing this statement.

 List column must be NULL to insert a new list

 Explanation:  An attempt was made to insert a new list into an
 existing list.

 User Action:  First delete the list with the DELETE LIST
 statement.

 Column referenced in List Cursor is ambiguous in Table Cursor

 Explanation:  The field specified in the list cursor select
 statement was mentioned in more than one select expression in
 the table cursor definition.

 User Action:  Specify a table cursor where the list reference
 isn't ambiguous.

 Maximum number of columns for table in SELECT * is <value>

 Explanation:  You used the column wildcard (*) in the select
 list for a table that has too many columns.

 User Action:  Name a subset of the columns explicitly in the
 select expression.

 Maximum allowed statement nesting level exceeded

 Explanation:  You exceeded the maximum allowed nesting of
 subqueries.

 User Action:  Reduce the nesting level.

 Maximum number of tables allowed in SELECT exceeded

 Explanation:  You exceeded the maximum number of tables allowed
 in the FROM clause of a select expression.

 User Action:  Reduce the number of tables named in the FROM
 clause.

 Minimum mapping value greater than maximum value

 Explanation:  You have supplied a minimum mapping value that is
 larger than    the maximum mapping value.

 User Action:  Correct the error and try the command again.

 <text> must have a value

 Explanation:  No value was specified for a qualifier that was
 which must have a value.

 User Action:  Correct the command line syntax error, specifying
 a value for the qualifier.

 Incorrect STORE CLAUSE type for this storage map

 Explanation:  You specified a LIST storage clause when altering
 a table        storage map or a TABLE storage map option when
 altering a     LIST storage map.

 User Action:  Only try to change attributes which are
 appropriate for the    kind of storage map you are altering

 Relation <text> has no valid columns to move

 Explanation:  None of the fields for the specified relation
 could be moved.  Each of those invalid fields caused a warning
 message to be displayed, but with no valid fields remaining, the
 transfer definition may not proceed.

 User Action:  Re-enter the transfer definition with one or more
 valid columns.

 Host variable <text> is a multi-dimensioned array

 Explanation:  The SQL precompilers do not support references to
 multi-dimensioned arrays.

 User Action:  Assign the value in the multi-dimensioned array to
 a field which is not in a multi-dimensioned array before using
 it in an SQL statement or passing it into a module language
 procedure.

 Attribute is specified redundantly

 Explanation:  You specified a field attribute more than once.
 Because SQL can not determine which attribute to use, it rejects
 it.

 User Action:  Respecify the definition without the redundant
 clauses.

 Multiple specified attribute.  "<text>" was specified more than
 once

 Explanation:  An attribute was specified more than once in a
 conflicting manner.

 User Action:  Remove conflicts and try the statement again.

 Host variable <text> is based on a structure defined more than
 once.

 Explanation:  The named host variable is based on a structure
 that is defined more than once in the file being precompiled.
 Either the user defined the structure more than once in a single
 C procedure (which is illegal in any C program), or there is
 more than one procedure that defines the structure (legal in C,
 but the SQL C precompiler does not recognize that the structures
 are in two different procedures and generates this error).

 Multiple UIC in ACL entry

 Explanation:  You used more than one user identification code
 (UIC) in an ACL entry.

 User Action:  Use only one UIC in ACL entry.

 <text> cannot be a target for more than one move clause

 Explanation:  The user entered a transfer with more than one
 move clause specifying the named target as the target.  Note
 that even if an into clause is not specified, the target name,
 taken from the source table name, must be unique.

 User Action:  Re-enter the statement making sure that tables
 specified in INTO clauses are unique and do not duplicate names
 of source tables without INTO clauses.

 no MOVE RELATION clause is specified in an EXTRACTION ROLLUP
 transfer

 Explanation:  In a CREATE TRANSFER statement of an EXTRACTION
 ROLLUP transfer, you have not specified any MOVE RELATION
 clause.

 User Action:  Since a MOVE RELATIONS ALL clause is not allowed
 in this context, you have to explicitly specify the MOVE
 RELATION clauses.  Reenter the CREATE TRANSFER statement by
 specifying the MOVE RELATION clauses explicitly.

 the database pathname <text> is the same as another dictionary
 entity

 Explanation:  The name chosen for the database is the same as
 another dictionary entity of a different type.

 User Action:  Choose a different name.

 The name <text> is longer than the <value> character maximum

 Explanation:  You specified a name which is longer than the
 maximum supported length for names in this context.

 User Action:  Use a shorter name.

 Host variable <text> has a negative dimension.

 Explanation:  The size of this array is less than or equal to
 zero.

 User Action:  Only use positive dimensions.

 Functions may not be nested

 Explanation:  Functions cannot contain other functions in their
 arguments.  For example, AVG(COUNT(DISTINCT(CITY)) is illegal.

 User Action:  Do not nest functions.

 Cannot include file <text> from another included file

 Explanation:  You attempted to nest INCLUDE file-spec
 statements.  Source code files specified in an INCLUDE file-spec
 statement cannot themselves contain nested INCLUDE file-spec
 statements.

 User Action:  Move the INCLUDE statement to the main program.

 Column select expression was expected

 Explanation:  You supplied something besides a column select
 expression where SQL expected one.

 User Action:  Correct the syntax error.

 LIMIT TO clause is not valid in an INSERT or LIST CURSOR

 Explanation:  It is illegal to specify a LIMIT TO clause in an
 INSERT or LIST CURSOR.

 User Action:  Remove the LIMIT TO clause.

 aggregate expressions are not allowed in MOVE RELATION clauses

 Explanation:  You entered a MOVE RELATION clause that contained
 an aggregate expression.  The MOVE RELATION clause only allows
 an operator, literal value, or field name.

 User Action:  Check the VAX Data Distributor Handbook or the VAX
 Rdb/VMS Reference Manual for details on the MOVE RELATION
 clause.  Reenter the CREATE TRANSFER statement with a correct
 MOVE RELATION clause.

 No attributes specified for ALTER <text>

 Explanation:  The user specified an ALTER DOMAIN statement or an
 ALTER TABLE ALTER column-name clause without specifying any
 attributes.

 User Action:  Specify something to change.

 ANY and UNIQUE are not allowed in a MOVE RELATION clause

 Explanation:  You entered a MOVE RELATION clause containing ANY
 or UNIQUE.  The MOVE RELATION clause only allows an operator,
 literal value, or field name.

 User Action:  Check the VAX Data Distributor Handbook or the VAX
 Rdb/VMS Reference Manual for details on the MOVE RELATION
 clause.  Reenter the CREATE TRANSFER statement with a correct
 MOVE RELATION clause.

 BATCH UPDATE is not allowed without setting of <text> logical
 name

 Explanation:  BATCH UPDATE transactions are not allowed with 2PC
 turned on.  2PC is only turned off by setting the logical name
 named in the message to "TRUE".

 User Action:  If you want to migrate the application without the
 use of of context items (i.e.  2PC/DDTM) and allowing BATCH
 UPDATE transactions, define the logical name to "TRUE".
 Otherwise, you should change the BATCH UPDATE option to another
 transaction option.

 BATCH_UPDATE is not supported in the SQL interface to Rdb/VMS

 Explanation:  A DECLARE TRANSACTION statement specified the
 BATCH_UPDATE transaction mode.  The SQL interface to Rdb/VMS
 does not support BATCH_UPDATE.

 User Action:  Replace BATCH_UPDATE with READ_WRITE reserving the
 tables you want to update with EXCLUSIVE WRITE locking.

 export file <text> not created

 Explanation:  An error has occurred during creation of the
 EXPORT file.

 User Action:  Follow actions directed by the corresponding RMS
 error.

 you cannot EXPORT a database from within a transaction

 Explanation:  You typed EXPORT from inside a transaction.

 User Action:  End the transaction and try again.

 BATCH UPDATE not allowed in procedure with CONTEXT parameter

 Explanation:  Your source contains a SET TRANSACTION statement
 in a procedure which will have a context parameter added to it.
 This is not allowed.

 User Action:  Change the transaction options to use something
 other than BATCH UPDATE or compile the module without the
 /CONTEXT=ALL qualifier or remove the name of this procedure from
 the list of procedures to receive a context parameter.

 BATCH UPDATE not allowed in statement with USING CONTEXT

 Explanation:  Your source contains a SET TRANSACTION statement
 with a USING CONTEXT clause.  This is not allowed.

 User Action:  Change the transaction options to use something
 other than BATCH UPDATE or remove the USING CONTEXT clause from
 the statement.

 There is no data dictionary on this system.  Specify FILENAME in
 the DECLARE SCHEMA statement

 Explanation:  You declared a schema with a data dictionary path
 name, but there is no data dictionary running on this system.
 You must declare a schema using a file name.

 User Action:  Declare the schema with the database file name.

 There is no data dictionary on this system.  Specify FILENAME in
 the ALTER SCHEMA statement

 Explanation:  You altered a schema with a data dictionary path
 name, but there is no data dictionary running on this system.
 You must alter a schema using a file name.

 User Action:  Alter the schema with the database file name.

 the data dictionary will not be updated

 Explanation:  You cannot store the database information in the
 data dictionary.  See the following message.

 User Action:  Correct the problem and try the operation again.

 Schema invoked by filename, the data dictionary will not be
 updated

 Explanation:  You issued a data definition statement after
 invoking by file name

 User Action:  This is a warning.  You can ROLLBACK and invoke
 the schema by specifying the path name.  This ensures that data
 definitions are updated both in the data dictionary and in the
 schema itself.

 computed field <text> in relation <text> not imported

 Explanation:  You specified a computed field in your database
 that could not be imported.  Perhaps the field references other
 fields and relations that were deleted from the database by an
 older version of the software that would have permitted such a
 thing.

 User Action:  You must investigate the problem further.  The
 table should have been properly imported except for the listed
 column.

 <text> interpreted as column name where none are allowed

 Explanation:  An expression included a string SQL interpreted as
 a column name where a column name does not make sense.  For
 example, specifying a column name in the VALUES clause of an
 INSERT statement generates this error.  Or, omitting quotes
 around a string literal can also generate this error.

 User Action:  Replace the string with a quoted literal or host
 variable, or use a different form of the statement which will
 allow column names.

 Specifying a column list is incompatible with WHERE CURRENT OF

 Explanation:  It is illegal to specify both a column list and
 WHERE CURRENT OF.

 User Action:  Remove one of the clauses.

 This view definition must explicitly list column names

 Explanation:  You must specify names for all the columns in a
 view if the select expression in the view definition uses
 statistical functions or arithmetic expressions to create
 columns not in the source tables.

 User Action:  Explicitly name each coulumn in the view
 definition.

 Unable to import collating sequence <text>

 Explanation:  SQL could not import this collating sequence.  See
 the following message.

 User Action:  Correct the problem and try the operation again.

 Cannot create <text> constraint name for table <text>

 Explanation:  SQL tried to create a unique name for a CHECK type
 constraint on the named table.  SQL could not generate a unique
 name for this table.

 User Action:  You can either delete all CHECK constraints for
 this table and then recreate all of the constraints or you can
 specify the DIAGNOSTIC parameter to give the constraint an
 explicit name.

 unable to import constraint <text>

 Explanation:  Could not import this constraint -- see the
 message that follows.

 User Action:  Correct the problem and try the operation again.

 There are no matching columns in the corresponding select lists

 Explanation:  You specified a UNION CORRESPONING query
 expression in which there were no corresponding columns in the
 two select lists.  There must be at least one column which
 matches.

 User Action:  Either omit the CORRESPONDING keyword, or specify
 at least one pair of columns which match.

 Unable to import privileges on column <text>.<text> for <text>

 Explanation:  SQL could not import these privileges -- see the
 message that follows.

 User Action:  Correct the problem and try the operation again.

 A list specification must have a WHERE CURRENT OF clause

 Explanation:  A list specification requires a WHERE CURRENT OF
 clause and one wasn't specified.

 User Action:  Specify the WHERE CURRENT OF clause.

 No DATA DIVISION found in COBOL program.

 Explanation:  Every COBOL program that uses embedded SQL must
 have a DATA DIVISION statement.  None was found in your input
 file.

 User Action:  Add a DATA DIVISION statement to your program.

 remaining data for this relation will be ignored

 Explanation:  An error occurred while you attempted to store the
 data; see the following message.

 User Action:  Correct the problem and try the operation again.

 database handles are not allowed in a MOVE RELATION clause

 Explanation:  You specified a database handle for the record
 selection expression (RSE) in a MOVE RELATION clause.  Inside a
 MOVE RELATION clause, database handles are not allowed for the
 RSE.

 User Action:  Reenter the CREATE TRANSFER statement omitting the
 database handle name.

 database key references are not allowed in a MOVE RELATION
 clause

 Explanation:  You entered a MOVE RELATION clause that contained
 a database key or a host variable.  The MOVE RELATION clause
 only allows an operator, literal value, or field name.

 User Action:  Check the VAX Data Distributor Handbook or the VAX
 Rdb/VMS Reference Manual for details on the MOVE RELATION
 clause.  Reenter the CREATE TRANSFER statement with a correct
 MOVE RELATION clause.

 There is no DBKEY for a row in a result table with a GROUP BY

 Explanation:  A SELECT expression with a group by clause
 requested the  DBKEY.  There is no DBKEY for a row in a grouped
 table.

 User Action:  Remove the DBKEY reference.

 A schema name was not specified on a DECLARE SCHEMA statement

 Explanation:  You issued a DECLARE SCHEMA statement that did not
 specify a schema by file specification or data dictionary path
 name.

 User Action:  Check the syntax of the DECLARE SCHEMA statement.

 There is no default authorization identifier

 Explanation:  You specified a table name without an
 authorization identifier but there is no default authorization
 identifier.

 User Action:  Either declare a default authorization identifier,
 or include the authorization identifier for a schema you have
 declared in the table name.

 DISTINCT columns are not valid in an INSERT or LIST CURSOR

 Explanation:  It is illegal to specify DISTINCT in an INSERT or
 LIST CURSOR.

 User Action:  Remove the DISTINCT clause.

 view <text> cannot be specified more than once in a transfer
 definition

 Explanation:  You have specified a view name in both a
 move-relations-clause and in a move-views-clause.

 User Action:  Reenter the CREATE TRANSFER statement by
 specifying the view either in a move-relations-clause or in a
 move-views-clause but not in both.

 SQL does not support lists of files

 Explanation:  You specified a list of module language files on
 the module language command line, or a list of context files on
 the precompiler command line.  SQL does not support lists of
 files.

 User Action:  Specify only one language file and one context
 file on a command line.

 unable to import domain <text>

 Explanation:  Could not import this domain.  See the following
 message.

 User Action:  Correct the problem and try the operation again.

 FIRST clause is not allowed in MOVE RELATION clause of a
 REPLICATION transfer

 Explanation:  In the MOVE RELATION clause of a REPLICATION
 TRANSFER definition you have entered a FIRST clause.

 User Action:  Reenter the CREATE TRANSFER statement without the
 FIRST clause in the MOVE RELATION clause.

 GROUP BY clause is not valid in an INSERT or LIST CURSOR

 Explanation:  It is illegal to specify a GROUP BY clause in an
 INSERT or LIST CURSOR.

 User Action:  Remove the GROUP BY clause.

 unable to import index <text>

 Explanation:  Could not import this index.  See the following
 message.

 User Action:  Correct the problem and try the operation again.

 no implicit transaction to commit or rollback

 Explanation:  The commit or rollback statement was used without
 there being a valid implicit transactin outstanding.  Explicit
 transactions must be terminated via DDTM.

 User Action:  Do not use the commit or rollback statement unless
 there is an implicit transaction outstanding.

 The INCLUDE statement with the FROM DICTIONARY clause is not
 supported in <text>

 Explanation:  The INCLUDE statement with the FROM DICTIONARY
 clause is not  supported for languages which do not have an
 equivalent     statement in the language.  An example of this is
 Ada.

 User Action:  Remove the INCLUDE statement with FROM DICTIONARY
 clause.

 unable to define item from command line

 Explanation:  Could not define an item from the command line.
 See the following message.

 User Action:  Correct the problem and try the operation again.

 No input file specified

 Explanation:  You did not specify a file for the precompiler.

 User Action:  Enter the precompiler command line again,
 specifying a file this time.

 unable to import storage map <text>

 Explanation:  Could not import this storage map.  See the
 following message.

 User Action:  Correct the problem and try the operation again.

 <text> has no matching UNIQUE or PRIMARY KEY constraint

 Explanation:  You specified a referenced column list which does
 not match      the columns specified as the key for any UNIQUE
 or PRIMARY KEY         constraint.  The referenced column list
 must be an exact match         for the key of such a constraint.

 User Action:  Specify a referenced column list that matches a
 key for a      UNIQUE or PRIMARY KEY column, or define a UNIQUE
 or PRIMARY     KEY constraint that matches the referenced column
 list you       specified.

 attempt to move the relation <text> multiple times

 Explanation:  You attempted to specify the same relation name
 more than once in the MOVE clause of a CREATE TRANSFER
 statement.  In a CREATE TRANSFER statement, you cannot move the
 same relation more than once.

 User Action:  Reenter the CREATE TRANSFER statement omitting the
 duplicate MOVE RELATION clause.

 attempt to move the view <text> multiple times

 Explanation:  You attempted to move the named view more than
 once in a CREATE TRANSFER statement.  This action is not
 permitted.

 User Action:  Reenter the CREATE TRANSFER statement, specifying
 each view only once.

 No module file specified on command line

 Explanation:  A module language compiler command line must
 include the name of a module file to compile.  This command line
 did not.

 User Action:  Repeat the command line with the name of a module
 file you wish to compile.

 MOVE RELATIONS ALL clause is not allowed in an EXTRACTION ROLLUP
 transfer

 Explanation:  In a CREATE TRANSFER statement of an EXTRACTION
 ROLLUP transfer, you have specified a MOVE RELATIONS ALL clause.

 User Action:  Reenter the CREATE TRANSFER statement by
 specifying each relation explicitly in a MOVE RELATION clause.

 MOVE VIEWS clause is not allowed in an EXTRACTION ROLLUP
 transfer

 Explanation:  In a CREATE TRANSFER statement of an EXTRACTION
 ROLLUP transfer, you have specified a MOVE VIEWS clause.

 User Action:  Reenter the CREATE TRANSFER statement without the
 MOVE VIEWS clause.

 Noncontiguous arrays not supported.

 Explanation:  You have passed a parameter that is a
 noncontiguous array    to the module language.  SQL does not
 support noncontiguous  arrays.

 User Action:  Use contiguous arrays to pass data to the module
 language.

 Negated qualifiers may not have values

 Explanation:  You specified a value for a qualifier that was
 preceded by NO.

 User Action:  Correct the command line syntax error, removing NO
 or the value.

 Host variable <text> is ambiguous in the host file

 Explanation:  The ANSI and ISO SQL standards require that host
 variable       names be unique in the entire file being
 preprocessed.          The SQL interface to Rdb/VMS only
 requires it to be unique       in its language scope.  This host
 variable is not unique         in the file.

 User Action:  If it is important to have only standard features
 in your        program, you should change the name of this host
 variable       to make it unique in the file.

 Nonstandard use of lowercase

 Explanation:  This token contains lowercase characters.  The
 ANSI and ISO   SQL standards only supports lowercase character
 in quoted strings.

 User Action:  If it is important to have only standard syntax in
 your   program, you should correct this syntax.

 COBOL file is not ANSI format

 Explanation:  The file being processed by the SQL COBOL
 precompiler is not     in ANSI format, or, if it is in ANSI
 format, you did not    specified the /ANSI switch.  The ANSI and
 ISO SQL standards      require that all precompiled COBOL
 programs be in ANSI format.

 User Action:  If it is important to have your program in a
 standard format,       you should convert your program to ANSI
 format.        See the VAX COBOL Reference Manual for a
 definition of what     ANSI and TERMINAL formats are and how to
 convert between them.

 Column <text> has a nonstandard data type

 Explanation:  You referred to a column whose data type is not
 included       in the ANSI and ISO SQL standards.

 User Action:  If it is important to have only standard features
 in your        program, you should change the data types of
 these columns  to be an standard data type.

 The standard does not permit this data type conversion

 Explanation:  You are comparing, assigning or unioning to
 expressions with       different data types.  These two
 expressions must be converted  to a common data type.  The ANSI
 and ISO SQL standards do       not support this conversion.

 User Action:  If it is important to have only standard features
 in your        program, you should change your statement to use
 supported      conversions.

 The standard requires columns merged by UNION be identical

 Explanation:  The ANSI and ISO SQL standards require that
 columns which  are being merged into a single result column by a
 UNION  clause must have identical definitions; that is, they
 must   have the same data type, length, scale, and so on.  The
 column pointed to is not identical to the column with which
    it is being merged.

 User Action:  If it is important to have only standard features
 in your        program, you should change the data types of
 these columns  to be identical, or remove the UNION from your
 program.

 Cursor <text> has a nonstandard type

 Explanation:  You referred to a cursor of a type not included
  in the ANSI and ISO SQL standards.

 User Action:  If it is important to have only standard features
 in your        program, you should not use this type of cursor.

 The standard only permits one DISTINCT clause in a select
 expression

 Explanation:  You entered a select expression which either has
 two    functions with DISTINCT clauses, or has a DISTINCT clause
 for the entire select list and a DISTINCT in a function.
      The ANSI and ISO SQL standards do not support multiple
    distinct clauses.

 User Action:  If it is important to have only standard features
 in your        program, you should remove one of the distinct
 clauses.

 Nonstandard data type

 Explanation:  The data type indicated or the data type of the
 column indicated       is not included in the current ANSI and
 ISO standards for SQL.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 The SQL standard does not include the dynamic interface

 Explanation:  The syntax indicated is not included in the
 current ANSI and       ISO standards for SQL.  The standard does
 not define the         dynamic interface.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 Host variable <text> has a nonstandard declaration

 Explanation:  The ANSI and ISO SQL standards only require that a
 small subset of host language data declarations be
     supported.  The declaration for this host variable
         uses language features which the standards do not
 require.

 User Action:  If it is important to have only standard features
 in your        program, you should change the definition of this
 host   variable.

 Nonstandard name

 Explanation:  This name is not a valid name in the ANSI and ISO
 SQL    standards.  It is either longer than 18 characters
      or contains a $.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 Nonstandard syntax -- required keyword or clause omitted

 Explanation:  The syntax indicated is not included in the
 current ANSI and       ISO standards for SQL.  The standard
 requires a clause or   keyword which is optional in the SQL
    interface to Rdb/VMS.  You have omitted that        clause or
 keyword.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 The SQL standard does not specify the physical schema

 Explanation:  The syntax indicated is not included in the
 current ANSI and       ISO standards for SQL.  The standard does
 not define physical    objects.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 Nonstandard quote character

 Explanation:  This informational message is generated by either
 of two         situations:     - The ANSI and ISO SQL standards
 require the single quotation    mark (') character.  You used
 the double quotation mark (")   character.     - ANSI requires
 continuation be done by language rules, which   in COBOL means
 the first character on the line being   continued must be a
 double quotation mark (").  You used    a single quotation mark
 (').

 User Action:  If it is important to have only standard syntax in
 your   program, correct this syntax.

 Nonstandard scale.  Your scale (<value>) exceeds the precision
 (<value>)

 Explanation:  The scale specfied exceeds the precision.  The
 current ANSI   and ISO standards for SQL require a scale less
 than or equal  to the precision.

 User Action:  If it is important to have only standard syntax in
 your   program, you should have scale less than or equal to
 precision.

 The SQL standard does not include schema manipulation

 Explanation:  The syntax indicated is not included in the
 current ANSI and       ISO standards for SQL.  The standard does
 not define the         schema manipulation language.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 Nonstandard syntax

 Explanation:  The syntax indicated is not included in the
 current ANSI and       ISO standards for SQL.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 The SQL standard does not specify how to control transaction
 characteristics

 Explanation:  The syntax indicated is not included in the
 current ANSI and       ISO standards for SQL.  The standard does
 not specify how        transaction characteristics are to be
 defined.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 The standard only permits UNION outside of subqueries in DECLARE
 CURSOR

 Explanation:  You have included a UNION in a context in which
 the ANSI       and ISO SQL standards do not support.  Only
 DECLARE CURSOR         statements may have a UNION in the
 standard.

 User Action:  If it is important to have only standard features
 in your        program, you should remove this UNION clause.

 Nonstandard feature for integration with other Digital products

 Explanation:  The syntax indicated is not included in the
 current ANSI and       ISO standards for SQL.  This is a feature
 which is provided      for compatability with other Digital
 products such as       Datatrieve and CDD/Plus.

 User Action:  If it is important to have only standard syntax in
 your   program, you should remove this syntax.

 There is no OPEN procedure for cursor <text>

 Explanation:  There are no OPEN procedures for this cursor.  A
 module must have exactly one procedure which opens a particular
 cursor.

 User Action:  Add a procedure which opens this cursor.

 ORDER BY clause is not valid in an INSERT or LIST CURSOR

 Explanation:  It is illegal to specify a ORDER BY clause in an
 INSERT or LIST CURSOR.

 User Action:  Remove the ORDER BY clause.

 SQLDA is not supported in Pascal

 Explanation:  The Pascal precompiler does not support the SQLDA
 data structure         or the dynamic interface.

 User Action:  Remove all references to SQLDA in your program.
 If the SQL     Dynamic interface is required with Pascal, use
 the SQL module         language.

 No precompiler selected

 Explanation:  You invoked the precompiler without specifying the
 language option desired.

 User Action:  Specify a switch or file extension.

 Table <text> has no primary key

 Explanation:  You omitted the referenced column list in a
 referential    constraint for which the referenced table has not
 primary key.   If the referenced table has no primary key, you
 must specify   a column list which matches the columns in a
 unique constraint.

 User Action:  Add a referenced column list, or define a primary
 key for the    referenced table.

 SQL statements must follow a procedure declaration

 Explanation:  SQL statements must come after a procedure
 statement.  This statement was found before any procedure
 statement.

 User Action:  Put your SQL statements inside a procedure.

 insufficient privilege to transfer the view <text>

 Explanation:  You attempted to transfer the named view without
 READ privilege on the view.  You must have READ privilege on the
 view to be able to transfer the view in a CREATE TRANSFER
 statement.

 User Action:  Reenter the CREATE TRANSFER statement excluding
 the named view.  Check the VAX Rdb/VMS Reference Manual for
 details on PROTECTION statements.

 insufficient privilege to transfer the relation <text>

 Explanation:  You specified a relation for which you do not have
 READ privilege.  You must have READ privilege on the relation to
 transfer the relation in a CREATE TRANSFER statement.

 User Action:  Reenter the CREATE TRANSFER statement excluding
 the named relation.  Check the VAX Rdb/VMS Reference Manual for
 details on PROTECTION statements.  Also consult your database
 administrator.

 insufficient privilege to CREATE a replication transfer

 Explanation:  You attempted to CREATE a replication transfer
 without CREATE privilege on the source database.  To CREATE a
 replication transfer, you must have CREATE privilege on the
 source database.

 User Action:  Check the VAX Rdb/VMS Reference Manual for details
 on PROTECTION statements.  See your database administrator to
 obtain CREATE privilege.

 insufficient privilege to transfer the relation <text>.<text>

 Explanation:  You specified a relation for which you do not have
 READ privilege in the specified database.  You must have READ
 privilege on the relation to transfer the relation in a CREATE
 TRANSFER statement.

 User Action:  Reenter the CREATE TRANSFER statement excluding
 the named relation.  Check the VAX Rdb/VMS Reference Manual for
 details on PROTECTION statements.  Also consult your database
 administrator.

 GRANT or REVOKE specified only unsupported privileges

 Explanation:  A GRANT or REVOKE statement specified only
 unsupported DB2 privileges.  It has no effect.

 User Action:  None.  SQL ignores the statement.  However, to
 avoid this message, either remove the statement or add some
 supported privileges to it.

 REDUCE clause is not allowed in MOVE RELATION clause of a
 REPLICATION transfer

 Explanation:  In the MOVE RELATION clause of a REPLICATION
 TRANSFER definition you have entered a REDUCE clause.

 User Action:  Reenter the CREATE TRANSFER statement without the
 REDUCE clause in the MOVE RELATION clause.

 No relation found for map <text>

 Explanation:  The map name given has no table in the schema.

 User Action:  Use the correct map name.

 unable to import table <text>

 Explanation:  Could not import this table.  .  See the following
 message.

 User Action:  Correct the problem and try the operation again.

 remote node or version number is not allowed in a log file name

 Explanation:  You used a node name or a version number in the
 log file specification of a CREATE TRANSFER statement.

 User Action:  Reenter the CREATE TRANSFER statement using a log
 file specification that does not contain a node name or a
 version number.

 Specifying a RETURNING clause is incompatible with a positioned
 insert statement

 Explanation:  It is illegal to specify a RETURNING clause with a
 positioned insert.

 User Action:  Remove the RETURNING clause.

 Read only column expressions are not allows in an INSERT or LIST
 CURSOR

 Explanation:  A column expression specified something other than
 a simple column reference such as an expression.

 User Action:  Limit usage to only column names.

 <text> is not declared in procedure <text>

 Explanation:  You used the parameter as a runtime parameter for
 a filename or pathname in a DECLARE SCHEMA statement.  Such
 parameters must be declared in every procedure in the module,
 and must be character data types.  You did not declare this
 paramter in this procedure.

 User Action:  Declare the parameter as a character variable in
 the procedure.

 Nothing altered in ALTER SCHEMA statement

 Explanation:  There was nothing altered in the ALTER SCHEMA
 query.

 User Action:  Remove the query or modify it to alter schema
    characteristics.

 list storage area <text> is not defined

 Explanation:  You specified a storage area in the LIST STORAGE
 AREA clause that does not exist.

 User Action:  Specify a storage area which is already defined in
 the CREATE SCHEMA statement.

 SELECT FIELDS ALL clause is not allowed in an EXTRACTION ROLLUP
 transfer

 Explanation:  In a CREATE TRANSFER statement of an EXTRACTION
 ROLLUP transfer, you have specified a SELECT FIELDS ALL clause.

 User Action:  Reenter the CREATE TRANSFER statement by
 specifying each field explicitly in the SELECT FIELDS clause.

 Specifying a SELECT expression is incompatible with a positioned
 insert statement

 Explanation:  It is illegal to specify a SELECT expression with
 a positioned insert.

 User Action:  Specify only a VALUES clause.

 SORT clause is not allowed in MOVE RELATION clause of a
 REPLICATION transfer

 Explanation:  In the MOVE RELATION clause of a REPLICATION
 TRANSFER definition you have entered a SORT clause.

 User Action:  Reenter the CREATE TRANSFER statement without the
 SORT clause in the MOVE RELATION clause.

 Unable to import schema privileges for <text>

 Explanation:  SQL could not import these privileges; see the
 message that follows.

 User Action:  Correct the problem and try the operation again.

 No INCLUDE SQLCA statement was specified

 Explanation:  Every precompiled SQL program must have an INCLUDE
 SQLCA statement in it.  This program did not have one.

 User Action:  Add an INCLUDE SQLCA statement.

 Neither SQLCA nor SQLCODE were declared

 Explanation:  All precompiled SQL programs must include a
 definition for an SQL status variable.  This can be done by
 specifying an INCLUDE SQLCA statement or by defining an integer
 host variable name SQLCODE.  This program did neither.

 User Action:  Add either an SQLCODE variable or an INCLUDE SQLCA
 statement.

 Host variable <text> is based on an undefined structure

 Explanation:  The FORTRAN RECORD host variable declaration uses
 a structure name which has not be declared.

 User Action:  Either change the name of the structure this host
 variable is based on, or define a structure with that name.

 RECORD host variable <text> does not specify a structure name

 Explanation:  The FORTRAN RECORD host variable declaration does
 not specify the structure name which the record is based on.

 User Action:  Add the name of the structure this host variable
 is based on.

 Cursor <text> has not been declared

 Explanation:  You must declare a cursor before you refer to it
 in an OPEN, CLOSE, FETCH, UPDATE, or DELETE statement.

 User Action:  Declare the cursor, or use the name of a cursor
 which is already declared.

 Format DATE <value> does not exist.

 Explanation:  You entered DATE date-number where the logical
   LIB$DATE_FORMAT_nnn does not exist.

 User Action:  Contact system manager to install the date
 formats.

 Language <text> does not exist.

 Explanation:  You entered SET LANGUAGE statement, but the
 logical        name table LNM$LANGUAGE_xxx does not exist.

 User Action:  Contact your system manager to make sure
 everything     has been set up properly; the language may not be
 supported.

 Procedure <text> in CONTEXT list not defined

 Explanation:  The value of the /CONTEXT qualifier specified a
 procedure which was not defined in the body of the module.

 User Action:  Either add the procedure to the module or omit the
 offending procedure name from the /CONTEXT qualifier value list.

 Format TIME <value> does not exist.

 Explanation:  You entered TIME time-number where the logical
   LIB$TIME_FORMAT_nnn does not exist.

 User Action:  Contact system manager to install the date/time
 formats.

 replication transfer is not supported for this source database

 Explanation:  You attempted to create a replication transfer on
 a source database that is not an Rdb/VMS database.  Replication
 transfers can be created only for Rdb/VMS databases.  For other
 databases you can create only extraction transfers.

 User Action:  If your source database is not an Rdb/VMS
 database, create an extraction transfer.

 <text> is not a view

 Explanation:  The name you specified in a MOVE VIEWS clause is
 not the name of a view.

 User Action:  Retype the CREATE TRANSFER command with the
 correct view name.

 "<text>" is a DB2 feature not supported by the SQL interface to
 Rdb/VMS.

 Explanation:  This is a feature supported by DB2 that the SQL
 interface to Rdb/VMS does not support.

 User Action:  Remove references to this feature.

 Labelled durations are a DB2 feature not supported by SQL.

 Explanation:  The SQL interface to Rdb/VMS does not support
 labelled durations.

 User Action:  Remove references to labelled durations.

 DB2 function not supported by SQL.

 Explanation:  This is a function supported by DB2 that the SQL
 interface to Rdb/VMS does not support.

 User Action:  Remove references to this function.

 No rows were found for this statement

 Explanation:  No rows were found for an UPDATE or DELETE
 statement, or a query produced an empty table.

 User Action:  None, this is a warning message.

 Column <text> cannot be referred to in the select list or HAVING
 clause because it is not in the GROUP BY clause

 Explanation:  In the select list and HAVING clauses of select
 expressions containing the GROUP BY clause, you can refer only
 to those columns named in the GROUP BY clause.

 User Action:  Either add the column named in the message to the
 GROUP BY clause, or delete from the select list or HAVING
 clause.

 <text> is not a host variable

 Explanation:  The object referenced as a host variable was not a
 host variable.

 User Action:  Refer to a host variable.

 Cursor <text> is not an INSERT ONLY cursor

 Explanation:  In a positioned INSERT statement, the cursor named
 wasn't an INSERT ONLY CURSOR

 User Action:  Restrict usage of INSERT statements to INSERT ONLY
 CURSORS.

 Column, <text>, not specified in table cursor, <text>

 Explanation:  The list column specifed for a list cursor wasn't
 specified in the related table cursor.

 User Action:  Modify the table cursor to add the list column to
 the select list or modify the list cursor to use a different
 column.

 Column <text> is not of data type LIST

 Explanation:  The column named in the error message has a data
 type other than LIST.

 User Action:  Specify a column with the proper data type.

 Cursor <text> is not a list cursor

 Explanation:  An attempt was made to use a list INSERT statement
 into a table cursor.

 User Action:  Use the INSERT INTO CURSOR statement.

 Unable to import privileges on table <text> for <text>

 Explanation:  SQL could not import these privileges -- see the
 message that follows.

 User Action:  Correct the problem and try the operation again.

 Unable to IMPORT trigger <text>

 Explanation:  SQL could not import this trigger; see the message
 that follows.

 User Action:  Correct the problem and try the operation again.

 List cursor <text> is based on a different than table cursor
 <text>

 Explanation:  The table cursor named in the message references a
 table cursor that is based on a different table from the LIST
 cursor.

 User Action:  Base the list cursor on a table cursor that
 references that same table.

 Cursor <text> is not a table cursor

 Explanation:  You must declare list cursor to be the current of
 a table cursor.  The cursor specified in the WHERE CURRENT OF
 clause is another list cursor.

 User Action:  Reference a table cursor.

 Cannot use indicator variables in WHERE or HAVING

 Explanation:  You cannot use indicator variables in WHERE
 clauses or HAVING clauses.

 User Action:  Use the NULL keyword to test if a value is null.

 Domain reference in column <text> is illegal in a DECLARE TABLE
 statement

 Explanation:  You referred to a user defined domain in a DECLARE
 TABLE statement.  All domains in the DECLARE TABLE statement
 must be SQL predefined types.

 User Action:  Substitute the predefined equivalent of the user
 defined domain.

 <text> is not the name of a DSRI-compliant database

 Explanation:  You supplied the name of a schema that does not
 exist under this data dictionary directory, or you supplied a
 name that is not a DSRI-compliant database.

 User Action:  Supply the name of a valid database.

 Schema was not declared using PATHNAME.  Dictionary access is
 illegal.

 Explanation:  You tried to include a dictionary entity in the
 schema, but the schema itself is not using the dictionary.

 User Action:  Declare the schema using PATHNAME.

 The <text> being defined must be in the same schema as the
 <text> it references

 Explanation:  When creating an item, the item was named as part
 of one schema, but it was being created from items of another
 schema.  For example, trying to create an index in one schema
 from a table in another schema generates this error.

 User Action:  Create the item naming only items from the same
 schema.

 Authorization identifier <text> not permitted within definition
 of SCHEMA <text>

 Explanation:  You specified an authorization identifier of a
 schema that was other than the one for the schema being defined.

 User Action:  Create defintions only for a single schema in a
 CREATE SCHEMA statement.  Use the standalone CREATE statements
 for accessing other schemas.

 UNION is not valid in an INSERT or LIST CURSOR

 Explanation:  It is illegal to specify a UNIONS as an INSERT
 CURSOR.

 User Action:  Limit usage to only a single table.

 unable to import view <text>

 Explanation:  Could not import this view -- see the message that
 follows.

 User Action:  Correct the problem and try the operation again.

 view <text> is not allowed in MOVE RELATION clause of a
 REPLICATION transfer

 Explanation:  In the MOVE RELATION clause of a REPLICATION
 TRANSFER definition you have specified a view.

 User Action:  Reenter the CREATE TRANSFER statement without the
 view in the MOVE RELATION clause.  The view definition can be
 moved by specifying the view in the MOVE VIEWS clause.

 WHERE clause is not valid in an INSERT or LIST CURSOR

 Explanation:  It is illegal to specify a WHERE clause in an
 INSERT or LIST CURSOR.

 User Action:  Remove the WHERE clause.

 No access to the data dictionary.

 Explanation:  Access is not permitted to the data dictionary.
 Previous error message should indicate the reason.

 User Action:  Correct problem from previous error message.

 An empty command string was passed to PREPARE.

 Explanation:  A null command string was passed to PREPARE.

 User Action:  Pass a string to PREPARE that is not empty.

 You cannot declare a transaction while a transaction is active.

 Explanation:  There is a currently transaction in progress.  You
 cannot declare a transaction while a transaction is in progress.

 User Action:  Commit or rollback the current transaction before
 issuing another DECLARE TRANSACTION statement.

 <text> is being converted from DECIMAL to <text>.

 Explanation:  DECIMAL is not a supported data type.  SQL
 converts DECIMAL columns and types to a supported data type.

 User Action:  None.  This is an informational message only.

 DSRI does not support descending index segments

 Explanation:  You specified that a descending index segment;
 DSRI does not support descending index segments.

 User Action:  Remove the DESC clause from the index
 specification.

 You can only use DECLARE statements in a context file.

 Explanation:  You can only include DECLARE statements in a
 context file.  These statements include DECLARE TRANSACTION,
 DECLARE SCHEMA, and DECLARE TABLE.

 User Action:  Remove everything but DECLARE statements from the
 context file.

 No comment terminator found

 Explanation:  A PL/I begin comment was found (/*) and no
 corresponding end comment (*/) was found before the end of the
 program.

 User Action:  Insert the comment terminator.

 An EXEC SQL flag was found before the previous END-EXEC flag.

 Explanation:  The previous SQL statement was missing its
 END-EXEC flag.  Every COBOL SQL statement must be preceded by
 EXEC SQL and be terminated by END-EXEC.  A period may optionally
 follow the 'END-EXEC' flag.

 User Action:  Add an END-EXEC flag to the previous SQL
 statement.  Make sure that the END-EXEC flag has no embedded
 spaces, and that there is no COBOL terminator period before the
 END-EXEC flag.

 File <text> not found for input to the precompiler

 Explanation:  Attempted to open a nonexistent file.

 User Action:  Check the file specified.  Supply complete file
 specification.

 Could not find file <text> named in INCLUDE statement

 Explanation:  You attempted to include a nonexistent file.

 User Action:  Check the file specification in the INCLUDE
 statement.  Supply a complete file specification.  Note that the
 default file extension is .SQL.

 <text> is being converted from NUMERIC to <text>.

 Explanation:  NUMERIC is not a supported data type.  The SQL
 interface to Rdb/VMS converts NUMERIC columns or types to a
 supported data type.

 User Action:  None.  This is an informational message only.

 Context file <text> was not found for input to the precompiler

 Explanation:  Attempted to open a nonexistent context file.

 User Action:  Check the file specified.  Supply a complete file
 specification.

 The SQLDA cannot be used in FORTRAN or COBOL

 Explanation:  PL/I is the only host language that supports the
 SQLDA.  This means you can only use the PREPARE...INTO and
 DESCRIBE statements in PL/I programs.  The only dynamic features
 supported by COBOL and FORTRAN are EXECUTE IMMEDIATE and
 EXECUTE, OPEN, and FETCH with host variable lists.

 User Action:  Remove references to the SQLDA from COBOL and
 FORTRAN programs.

 Domain <text> does not exist in this schema

 Explanation:  You specified a domain that does not exist in the
 schema.

 User Action:  Check schema entity definitions for the valid
 schema type names.

 The values in the row are not available for this trigger

 Explanation:  You tried to refer to the values in the row that
 was    changed in a trigger action.  The values are not
 available in   an action if action does not specify FOR EACH ROW
 or is  triggered at a time when values are not supported.

 User Action:  Rewrite your trigger so that values are available
 or there       are no references to the values.

 No transaction outstanding

 Explanation:  You attempted to terminate a transaction with a
 COMMIT or a ROLLBACK when no transaction was outstanding.  SQL
 does not start a transaction when you issue a DECLARE
 TRANSACTION, but waits until it encounters the first statement
 that requires a transaction.

 User Action:  Execute a statement that requires a transaction
 before issuing COMMIT or ROLLBACK.  All statements except
 DECLARE TRANSACTION, DECLARE SCHEMA, CREATE SCHEMA, and DROP
 SCHEMA require transactions.

 <text> is being converted from UNSIGNED NUMERIC to <text>.

 Explanation:  UNSIGNED NUMERIC is not a supported data type.
 The SQL interface to Rdb/VMS converts NUMERIC columns or types
 to a supported data type.

 User Action:  None.  This is an informational message only.

 unable to recover BLR string

 Explanation:  Attempt to import a BLR list with more than one
 segment.

 User Action:  Submit an SPR with a copy of the Rdb/VMS
 interchange file (.RBR) that caused the error.

 Tried to store null into host variable with no indicator
 variable

 Explanation:  Null values can only be stored in host variables
 which have indicator variables.

 User Action:  Add an indicator variable to the host variable
 reference or make sure that no null values can be returned to
 it.

 Numeric column will be compared with string literal as text

 Explanation:  You tried to compare a text literal with a numeric
 column.  The numeric column is converted to text and the
 comparison is made from left-to-right, character by character.
 This can lead to unexpected results.  For example, the
 comparison N between "0001" and "0999", no matter what N is,
 will never be true, because N is converted to text without a
 leading zero and compared alphabetically with the two string
 literals.

 User Action:  None, as long as you understand the semantics of
 the operation.  You should be aware that the comparison will
 take place between text values.

 Number of host variables passed (<value>) does not match number
 of parameters (<value>)

 Explanation:  The number of host variables you passed in to an
 EXECUTE, OPEN, or FETCH statement does not match the number of
 parameter markers (question marks) in the PREPARE statement's
 command string.

 User Action:  Make sure the number of host variables matches the
 number of parameter markers in the PREPARE statement.  There are
 two ways to pass in host variables.  One, explicitly pass in a
 list of host variables in a USING list.  Or two, pass in an
 SQLDA in a USING DESCRIPTOR clause.  If you are using an SQLDA,
 you must specify in the SQLDA SQLN field the number of SQLVAR
 structures you have initialized to point to your variables.

 Number of items selected does not match number items in the INTO
 clause

 Explanation:  A SELECT statement must have as many values in the
 select list as there are in the INTO clause.

 User Action:  Enter the same number of columns in the select
 list and the INTO clause.  If you are using 'SELECT *', check
 the columns that are defined in the selected table.

 Numeric data in column <text> cannot be converted to a date data
 type

 Explanation:  Rdb will not allow numeric data types to be
 converted to date

 User Action:  Do not try it again.

 only one E character is permitted in an edit string

 Explanation:  An edit string contains more than one E character.
 Only one is allowed.

 User Action:  Redefine the edit string with only one E
 character.

 Only one DECLARE TRANSACTION statement is allowed per module

 Explanation:  You can use only one DECLARE TRANSACTION statement
 in a preprocessed module.  It must occur before the first
 executable statement (SELECT, INSERT, UPDATE, CREATE, etc.).

 User Action:  Only use one DECLARE TRANSACTION statement in a
 module.

 Only the first file in the list will be precompiled

 Explanation:  You specified a list of files to be processed.
 This list will be passed along to the compiler with the first
 file replaced by the generated language file.  However, only the
 first file in the list will be precompiled.

 User Action:  If more than one of the files has SQL statements,
 they must be precompiled in separate command lines.  If you want
 only the first file precompiled, then no user action is
 neccessary.

 Only first variable in qualified variable expression

 Explanation:  COBOL allows only the first variable in a
 qualification to be an array.  The preprocessors do not
 recognize the arrays of arrays constructs in FORTRAN, COBOL or
 BASIC.

 User Action:  Rewrite the query and check the appropriate
 language reference manual.

 Only one schema can be referred to in this statement

 Explanation:  You cannot use objects from more than one schema
 in a SELECT, UPDATE, DELETE or CREATE statement.  You can,
 however, refer to tables from one schema in an INSERT statement
 and refer to tables in another schema in the SELECT which
 provides the values for that INSERT statement if the insert
 statement is not part of a trigger definition.

 User Action:  Use separate statements for multiple schema
 access.

 Only one transaction allowed at a time

 Explanation:  Only one transaction is allowed at a time.  Note
 that SQL starts a transaction, even if none was previously
 declared, on the first data manipulation statement.

 User Action:  Issue a COMMIT or ROLLBACK statement to terminate
 the transaction, then declare another.

 Only a value list is valid in an INSERT LIST CURSOR statement

 Explanation:  The only valid expression is a value list.

 User Action:  Use only a VALUES expression.

 Only one list column may be specified

 Explanation:  The list specification specifies more than one
 column in the SELECT list.  List cursors are limited to
 processing only a single list.

 User Action:  DECLARE a separate list cursor for each list.

 Only one table may be specified in an INSERT or LIST CURSOR

 Explanation:  It is illegal to specify more than one table in an
 INSERT or LIST CURSOR.

 User Action:  Limit usage to specifying only a single table.

 Only one PSECT statement per module is supported

 Explanation:  The PSECT directive may only be used once per
 module.

 User Action:  Decide which PSECT statement is really desired and
 delete all others.

 unable to open <text> as the interchange file

 Explanation:  Could not access the Rdb/VMS interchange file
 (.RBR).

 User Action:  Correct the problem indicated by subsequent
 messages and try the operation again.

 Operator stack overflow

 Explanation:  The internal limit of the parsing operator stack
 was exceeded.

 User Action:  Submit an SPR with the query that caused the
 error.

 Parameter <text> in procedure <text> must be a character
 parameter

 Explanation:  You used the parameter as a runtime parameter for
 a filename or pathname in a DECLARE SCHEMA statement.  Such
 parameters must be declared in every procedure in the module,
 and must be character data types.  The parameter in this
 procedure is not a character data type

 User Action:  Declare the parameter as a character variable in
 the procedure.

 Parameters must not be qualified

 Explanation:  A reference to a parameter included qualifiers.
 You cannot qualify parameters.

 User Action:  Define the parameter in the procedure, or use a
 parameter name which is defined in the procedure.

 Parameter <text> passed by invalid descriptor class (<value>)

 Explanation:  The parameter was passed to a module language
 procedure by descriptor when parameter checking was enabled and
 the class of the descriptor was not a supported descriptor
 class.

 User Action:  Correct the argument in the host language program

 Parameter <text> has invalid data type:  <value> declared,
 <value> passed.

 Explanation:  The parameter was passed to a module language
 procedure with a different data type than it was declared in the
 procedure.  The codes for the data type as declared and as
 passed are specified in the message.  The codes are from the
 DSC$B_DTYPE from the descriptor.  See the "Introduction to VMS
 System Routines" manual for these codes.

 User Action:  Make the parameter agree in the module and the
 host language.

 Parameter <text> has invalid length:  <value> declared, <value>
 passed.

 Explanation:  The parameter was passed to a module language
 procedure with a different length than it was declared in the
 procedure.  The error message indicates the length of the
 parameter as declared in the module, and the length of the
 parameter passed at run-time.

 User Action:  Make the parameter agree in the module and the
 host language.

 Parameter <text> has invalid scale:  <value> declared, <value>
 passed.

 Explanation:  The parameter was passed to a module language
 procedure with a different scale than it was declared in the
 procedure.  The error message indicates the scale of the
 parameter as declared in the module, and the scale of the
 parameter passed at run-time.

 User Action:  Make the parameter agree in the module and the
 host language.

 Parameter <text> has a binary scale factor

 Explanation:  The parameter was passed to a module language
 procedure with a binary scale factor.  SQL supports only decimal
 scale factors.

 User Action:  Either do not use a scale factor, or use a data
 type with which your language uses decimal scale factors.  For
 example, PL/I uses binary scale factors with fixed binary data
 and decimal scale factors with fixed decimal data.  If you want
 to use scale factors, use fixed decimal.  Be sure to change the
 module to agree with the new data type.

 FETCH LIST statements require a parameter list

 Explanation:  The FETCH LIST statement requires that the user
 explicitly specify a parameter list.

 User Action:  Specify the parameter list.

 Parse stack overflow

 Explanation:  The internal limit of the parsing stack were
 exceeded.

 User Action:  Submit an SPR with the query that caused the
 error.

 Host variable <text> is based on a record type that is
 unsupported

 Explanation:  The host variable you referred to is based on a
 record type which is unsupported.

 User Action:  Use a different type defintion.

 Host variable <text> is based on a record type that uses
 variants

 Explanation:  The host variable you referred to is based on a
 record type which uses Pascal variants.  SQL does not support
 types which include variants.

 User Action:  Use a different type definition.

 PATHNAME clause necessary when the dictionary is required

 Explanation:  When you create a schema using the DICTIONARY IS
 REQUIRED       clause, then you must also specify the PATHNAME
 clause.

 User Action:  Change the CREATE SCHEMA statement to either add
 the    the PATHNAME clause or to remove the    DICTIONARY IS
 REQUIRED clause.

 it was physically exported on <text>

 Explanation:  Information about the Rdb/VMS interchange file
 (.RBR).

 User Action:  None.

 Computed column may not be a primary key

 Explanation:  You specified a primary key constraint for a
 computed       column, which does not support this constraint.

 User Action:  Remove the primary key constraint from this
 definition.

 The SQL package name has been changed from <text> to <text>

 Explanation:  The name of the ADA source file is used to
 generate the name of a SQL package.  Because the SQL package
 name is not a legal ADA name, the package name is changed to a
 legal ADA name.

 User Action:  If the SQL package name and declaration file must
 be the same name as the ADA source file, then change the name of
 the ADA source file.  If not, no user action is required.

 Column <text> is used in a primary or unique key but permits
 NULL values

 Explanation:  You specified a column in a primary or unique key
 definition     which permits NULL values.  The current ANSI and
 ISO SQL        standards require that only fields for which NOT
 NULL is        specified may be included in a primary or unique
 key.

 User Action:  If it is important to have only standard syntax in
 your   program, you should either remove the column from the
   primary or unique key, or add the NOT NULL attribute to
      the column.

 The host variable in the PREPARE FROM clause must be a string.

 Explanation:  A host variable in the FROM clause of a PREPARE
 statement must have a string data type.

 User Action:  In COBOL declare the variable to be PIC X(n).  In
 PL/I declare the variable to be CHAR(n).  In FORTRAN, declare
 the variable to be CHARACTER XYZ*n.

 Statement is syntactically incomplete

 Explanation:  You entered a syntactically incomplete statement.

 User Action:  Complete the statement before typing "RETURN".

 This statement may not be prepared with a context structure

 Explanation:  A PREPARE or EXECUTE IMMEDIATE with an embedded
 USING CONTEXT clause or in a module language procedure with a
 context parameter was passed a statement which may not be
 prepared with a context structure.

 User Action:  If you are using a precompiled program, remove the
 USING CONTEXT clause.  If you are calling a module language
 procedure, either remove the procedure name from the
 /CONTEXT=(...) list or, if /CONTEXT=ALL is used, pass a zero as
 the address of the context structure or fill the distributed TID
 portion of the context structure with zeroes.

 Cannot prepare or release statement name used by an open cursor

 Explanation:  You declared a cursor based on a prepared
 statement name and opened the cursor.  While that cursor was
 still open, you tried to prepare or release the same statement
 name.

 User Action:  Close the cursor or end the transaction before
 using a PREPARE or RELEASE statement with the same statement
 name.

 Table <text> already has a primary key

 Explanation:  You specified a primary key definition for a table
 which  already had one.  A table can have only one primary key.

 User Action:  Remove the primary key definition from the
 statement, or delete   the existing primary key before executing
 the statement.

 Segmented String id for <text> will be displayed

 Explanation:  One of the columns specified in the select list of
 a SELECT statement is a list.  SQL does not support the Rdb
 Segmented String data type, but displays the segmented string
 identifier for interactive SELECT statements.  The segmented
 string identifier is an internal value which will probably not
 be meaningful.

 User Action:  Ignore the values displayed for the segmented
 string column.

 Procedure <text> has neither an SQLCA nor SQLCODE parameter

 Explanation:  A module language procedure must have either an
 SQLCA or an SQLCODE parameter declared.  This procedure had
 neither.

 User Action:  Add either an SQLCODE or SQLCA parameter.

 Preprocessed SELECT statements must include an INTO clause

 Explanation:  A preprocessed SELECT statement needs a place to
 put the data it retrieves.  An INTO clause is required to
 specify where to put the data.

 User Action:  Add an INTO clause to the SELECT statement.

 Data type unknown due to previous errors

 Explanation:  Due to previous errors, the precompiler or module
 language compiler does not understand either side of an
 assignment.

 User Action:  Correct errors previously reported, and recompile.

 Host variable <text> is a pointer variable which is illegal in
 SQL statements.

 Explanation:  The named variable is defined as a C pointer
 variable.  These variables are currently not supported by the C
 precompiler.

 User Action:  Use a different variable.

 Attempt to put to an opened list

 Explanation:  You attempted to do a SEGSTR.PUT using a handle
 returned by a SEGSTR.OPEN statement.  You can only do
 SEGSTR.GETs using the handle returned by open.

 User Action:  Specify the correct handle

 An invalid value <text> was specified for <text>

 Explanation:  You specified an invalid value for a command line
 qualifier

 User Action:  Correct the command line syntax error.

 The <text> qualifier does not take a value

 Explanation:  You specified a value for a command line qualifier
 which cannot have a value.

 User Action:  Correct the command line syntax error.

 Operation supported for Rdb/VMS databases only

 Explanation:  You issued a GRANT or REVOKE statement on a
 non-Rdb/VMS database.  The SQL interface to Rdb/VMS supports
 GRANT and REVOKE for Rdb/VMS databases only.

 User Action:  Do not issue any GRANT or REVOKE statements with
 this database.

 A READ_ONLY transaction can not specify write locks.

 Explanation:  The transaction was specified as READ_ONLY but a
 table in the RESERVING clause was locked for write access.  This
 is a conflict of access modes.

 User Action:  Declare the transaction READ_WRITE or use a read
 lock.  Note that the default is always READ_WRITE.

 You specified other attributes in addition to READ ONLY

 Explanation:  You specified other attributes in addition to READ
 ONLY   in the ALTER STORAGE AREA clause.  If you specify READ
 ONLY, you      cannot include other attributes in the same
 statement.

 User Action:   Specify the other attributes in separate ALTER
 SCHEMA         statements.

 size of edit string exceed internal data structure limits

 Explanation:  The length of an edit string exceeds the size of
 the internal data structures that used to represent it.

 User Action:  Temporarily reduce the size of the edit string and
 submit an SPR including a description of the table and domains
 that produce this error.

 Referencing column <text> and corresponding referenced column
 <text> do not match

 Explanation:  A referencing column and its corresponding
 referenced column must have the same data type, size and scale.
 These 2 columns do not.

 User Action:  Specify a referential constraint where the columns
 all match.

 The referencing and referenced columns have different lengths

 Explanation:  The referencing column list and the referenced
 column list (explicit or implicit) must have the same number of
 columns.  They do not for this referential constraint.

 User Action:  Change the lists to match.

 Table name <text> was not qualified and is in multiple schemas

 Explanation:  You must qualify a table name with an
 authorization identifier when accessing more than one schema
 containing that table name.

 User Action:  Make sure the DECLARE SCHEMA statements for the
 schema include authorization identifiers and retype the query
 using the appropriate authorization identifier.

 Table <text> is not defined in schema

 Explanation:  The specified table does not exist in the current
 schema.

 User Action:  Declare the correct schema.  Spell the table name
 correctly.  You may have specified a name other than a table
 name.

 Table <text> already exists in this schema

 Explanation:  You attempted to create a table with the name of
 an existing table

 User Action:  Choose a different name.

 a remote source database is not allowed to be replicated

 Explanation:  You were attached to a database on a remote node
 when you tried to create a replication mode transfer using the
 CREATE TRANSFER statement.

 User Action:  Create an extraction transfer instead of a
 replication mode transfer.

 REORGANIZE is only legal with ALTER STORAGE MAP

 Explanation:  You specified the REORGANIZE clause in a statement
 other than ALTER STORAGE MAP.

 User Action:  Remove the REORGANIZE clause.

 terminating the IMPORT operation

 Explanation:  The IMPORT operation has been aborted; see the
 messages preceding this one.

 User Action:  None.

 <text> is a keyword.  It cannot be used as a name

 Explanation:  You entered a keyword where a name was expected.

 User Action:  Specify a unique name instead of the keyword.

 The retry count must be positive

 Explanation:  The count specified in the RETRY clause of the
 CREATE SCHEDULE statement must be positive.

 User Action:  Re-enter the schedule definition with a positive
 retry count.

 REVOKE ENTRY is not supported for databases with ANSI privileges

 Explanation:  You executed a REVOKE ENTRY statement in a
 database that has ANSI style privileges.  There are no entries
 in ANSI style privileges so this is not supported.

 User Action:  Execute the statement again specifying the
 privileges you would like to revoke.

 EVERY or RETRY EVERY must not specify an absolute time

 Explanation:  You entered an absolute time for the EVERY or
    RETRY EVERY clause of the CREATE SCHEDULE statement.

 User Action:  Use a delta time or, for the EVERY clause, use a
 day of         the week, DAY, WEEK, or MONTH.

 List area <text> referred to but not defined

 Explanation:  The CREATE SCHEMA statement indicated that lists
 must be stored in a specific storage area, but that storage
    area was never created.

 User Action:  Change the CREATE SCHEMA statement to include a
 CREATE STORAGE         AREA statement with the name referred to
 by the         LIST clause.

 Cannot use a list in an expression

 Explanation:  You attempted to use a list column in an
 expression.  Segmented strings may be used only in expressions
 using the NULL operator.

 User Action:  Remove the operations on the list from the DML
 query.

 The result of a singleton select returned more than 1 value

 Explanation:  A singleton select statement (SELECT...INTO) may
 only return 1 row of values.  The result table for this
 singleton select contains more than one row.

 User Action:  Either embed the SELECT statement (without the
 INTO clause) in a DECLARE CURSOR statement and process it with
 OPEN and FETCH statements, or modify the SELECT statement so it
 will return only one row.

 A severe error was detected

 Explanation:  This is the exit status for a preprocessor when a
 severe error is detected.

 User Action:  Fix the error.

 descending

 Explanation:  Used in the SHOW INDEXES statement --

                                size of index key is <value>

 Explanation:  Used to display the number of characters used in
 the key for an index.  The size of index key is the minimum
 length for the column used for the key.

 User Action:  None.

                                mapping values <text> to <text>

 Explanation:  Uses values from <low> to <high> to minimize space
 needed for index node.

 User Action:  None.

 this space for hire

 Explanation:  Uses values from <low> to <high> to minimize space
 needed for index node.

 User Action:  None.

 Storage Map for table <text>.<text>:

 Explanation:  Used in SHOW TABLE

 Altering column <text> to a smaller data type may cause data
 loss

 Explanation:  Altering a column to a smaller data type might
 cause data     already stored in that column to appear lost.

 User Action:  None.  This is a warning message only.

 A space is required before file specification

 Explanation:  A space is required to parse the begining of the
 file specification.

 User Action:  Run the preprocessor again and include a space
 before the file specification.

 Space management options not valid on areas with uniform page
 format

 Explanation:  Space management options of thresholds, interval
 or both        were specified for an area with a uniform page
 formats.

 User Action:  Remove the space management option(s) from the
 storage area   with uniform page format, or change the storage
 area with      the specified space managment option(s) to have
 mixed page     format.

 SQLDA not large enough (<value>) to handle number of parameters
 (<value>)

 Explanation:  The SQLDA passed to PREPARE or DESCRIBE is not
 large enough to handle all of the parameters in the associated
 PREPARE command string.

 User Action:  Allocate an SQLDA to be large enough to have one
 SQLVAR for each input or output parameter ('?') in the PREPARE
 command string.  Then set SQLN to indicate the number of SQLVARs
 in the SQLDA.

 An SQLDATA field in the SQLDA was not initialized

 Explanation:  You passed in an SQLDA with a SQLDATA value of
 zero in one of the SQLVAR blocks.

 User Action:  You must enter nonzero values in every SQLDATA
 field in the prepared command string that SQLD indicates is
 necessary.

 An invalid SQLTYPE value of <value> was found in the SQLDA

 Explanation:  You passed in an SQLDA with a illegal SQLTYPE
 value.

 User Action:  You must enter a valid SQLTYPE value in every
 SQLTYPE field in the prepared command string that SQLD indicates
 is necessary.

 The segmented string ID for column <text> is <value> bytes, host
 variable must be the same size or larger.

 Explanation:  The host variable you are using with the DBKEY is
 not the        same size as the dbkey.

 User Action:  Allocate a host variable which is the correct
 size.

 The '<text>' statement has not been defined

 Explanation:  You attempted to use a statement name in an
 EXECUTE or a DESCRIBE statement that had not been used in a
 PREPARE statement.

 User Action:  Prepare a statement name before using it in an
 EXECUTE or a DESCRIBE statement.

 Cursor can only be used with prepared SELECT statements

 Explanation:  You attempted to declare a cursor based on a
 prepared statement that was not a SELECT statement.  Cursors can
 be based only on SELECT statements.

 User Action:  Use EXECUTE to execute this statement.

 The standard requires a column in this context

 Explanation:  The ANSI and ISO SQL standards require that you
 specify        a column which is not in an expression in this
 context.

 User Action:  If it is important to have only standard features
 in your        program, you should change your querry to use a
 column here

 Invalid use of asterisk - expected column name

 Explanation:  You attempted to use the column wildcard (*) where
 SQL requires an explicit column name.

 User Action:  Supply the names of the columns to be referenced.

 Nonstandard update of read-only cursor <text>

 Explanation:  In the ISO and ANSI standards for SQL, a cursor is
 read-only      if it includes an ORDER BY clause.  Read-only
 cursors cannot         be used in UPDATE or DELETE statements.

 User Action:  If it is important to have only standard features
 in your        program, you should change the cursor to not
 include the ORDER      by clause, or not use it in an UPDATE or
 DELETE statement.

 Cannot declare a second cursor based on statement <text>

 Explanation:  A prepared statement can only have one cursor
 based on it.  You tried to declare a second cursor based on the
 same prepared statement name used in a previous DECLARE CURSOR
 statement.

 User Action:  Remove one of the cursor definitions from your
 program or base the second cursor on a different statement name.

 Not enough columns were specified in the USING clause

 Explanation:  There were more literals specifed in the LIMIT
 clause of      the storage map than there were columns in the
 USING clause.

 User Action:  Either specify more columns in the USING clause,
 or reduce the  number of literals in the LIMITS clause.

 Column specified in STORE clause, <text>, is unknown to table
 <text>

 Explanation:  A column that did not exist in the table was used
 in the         CREATE STORAGE MAP statement.

 User Action:  Specify a valid column name.

 Table specifed in store clause, <text>, is unknown to this
 schema.

 Explanation:  The table named in the CREATE STORAGE MAP
 statement does not     exist in the schema.

 User Action:  Specify a valid table name.

 Host variable <text> is either a structure array or in a
 structure array

 Explanation:  The SQL precompilers do not support references to
 fields in a structure array (a host structure defined as an
 array).

 User Action:  Assign the value in the structure array to a field
 which is not in a structure array before using it in an SQL
 statement.

 String literal will be converted to numeric

 Explanation:  You tried to store a text literal into a numeric
 column.  The string literal will be converted to a numeric data
 type, if possible.

 User Action:  None.  However, if the string literal cannot be
 converted to a numeric data type, an error will result.

 Host structure <text> used in a value expression

 Explanation:  SQL statements can only refer to a host structure
 in contexts where the host structure can be expanded to a list
 of values.  A value expression requires a single value, so host
 structures cannot be used there.

 User Action:  Replace the host structure with an elementary
 item.

 A string literal was expected

 Explanation:  A string literal was expected but something else
 was found.

 User Action:  Correct the syntax error.

 String literal missing closing quote

 Explanation:  The string in a user assignment statement is
 missing a closing quote.

 User Action:  Insert one or more quotes as appropriate.

 The <text> structure has more elements than the <text> indicator
 vector

 Explanation:  The specified structure has more elements than the
 indicator vector it is associated with.

 User Action:  Make the indicator vector larger.

 String literal is too big

 Explanation:  You entered a string literal with a length greater
 than 1024 characters.  The length of a string literal must be
 less than or equal to 1024 characters.  A likely cause of this
 error is an unmatched quote mark.

 User Action:  Put missing quote marker, or use a string literal
 with no more than 1024 characters.

 String expression must not be longer than <value>

 Explanation:  The string expression must be shorter than the
 specified      length.  For example a database filespec must be
 less than      255 characters.

 User Action:  Specify a shorter string expression.

 A string expression was expected

 Explanation:  A string literal, a character host variable, or
 USER was expected but something else was found.  (Note that USER
 is not permitted in EXECUTE IMMEDIATE, and specifying it will
 also generate this message.)

 User Action:  Correct the syntax error.

 Subqueries in basic predicates cannot use GROUP BY

 Explanation:  A subquery used in a basic predicate, such as
 WHERE CITY = (SELECT ...), cannot contain the GROUP BY clause.
 The ANSI standard does not support this.

 User Action:  If it is important to have only standard SQL
 statements in your program, remove the GROUP BY clause or change
 the predicate to include ANY or ALL.

 Column select expression specifies too many columns

 Explanation:  A column select expression may only fetch one
 value unless it is in an EXISTS predicate.  This means any
 column select expression that uses the column wildcard (*) must
 have only one-column tables in its FROM clause.

 User Action:  If you specified more than one column explicitly,
 remove all but one.  If you used a wildcard, explicitly name a
 single column instead.

 One of the following symbols was expected:

 Explanation:  You typed an unexpected keyword.

 User Action:  Type a correct keyword.

 Syntax error

 Explanation:  A syntax error was detected in a your SQL
 statement.

 User Action:  Correct the syntax error and try the statement
 again.

 Page format for system relations cannot be MIXED

 Explanation:  The system relations for Rdb/VMS must be placed in
 an area        that contains the uniform page format.

 User Action:   Either create a separate storage area for
 RDB$SYSTEM or change   the default page format to uniform.

 Page format for system relations being changed to UNIFORM

 Explanation:  The storage area that contain the system relations
 must   have UNIFORM page formats.  Either through the use of the
 defaults, or by directly specifing PAGE FORMAT IS MIXED,
       SQL has been told to use MIXED page format for the area
  containing the system relations.  SQL is overriding that
      to UNIFORM pages.

 User Action:  Nothing.  This is an informational message.  The
 user might     want to change the command if it originated in a
 command        file.  This may avoid confusion later.

 <text> TINYINT <text>

 Explanation:  Displays an unscaled BYTE field definition --

 <text> TINYINT(<value>) <text>

 Explanation:  Displays a scaled BYTE field definition --

 <text> NUMERIC(<value>,<value>) <text>

 Explanation:  Displays an unscaled word field definition --

 <text> UNSIGNED NUMERIC(<value>,<value>) <text>

 Explanation:  Displays a scaled word field definition --

 <text> DECIMAL(<value>,<value>) <text>

 Explanation:  Displays an unscaled word field definition --

 Access is:  Read only

 Explanation:  Used in SHOW STORAGE AREA

 Access is:  Read write

 Explanation:  Used in SHOW STORAGE AREA

 <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Comment <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Definition for transfer <text>:

 Explanation:  Used in the SHOW TRANSFER statement.

 Definer <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 No definition found

 Explanation:  Used in the SHOW TRANSFER statement.

 Retry frequency <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 To <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Epilogue file <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Transfers in transfer monitor database

 Explanation:  Used in the SHOW TRANSFER statement.

 Information for transfer <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 End of information for transfer <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Last executed <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 *-

 Explanation:  Used in the SHOW TRANSFER statement.

 Log file <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Type EXTRACTION

 Explanation:  Used in the SHOW TRANSFER statement.

 Type EXTRACTION ROLLUP

 Explanation:  Used in the SHOW TRANSFER statement.

 Type REPLICATION

 Explanation:  Used in the SHOW TRANSFER statement.

 Next transfer <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 No epilogue file

 Explanation:  Used in the SHOW TRANSFER statement.

 No log file

 Explanation:  Used in the SHOW TRANSFER statement.

 No transfers found

 Explanation:  Used in the SHOW TRANSFER statement.

 <text> No privilege for SHOW

 Explanation:  Used in the SHOW TRANSFER statement.

 No prologue file

 Explanation:  Used in the SHOW TRANSFER statement.

 Last completion status Transfer has never executed successfully

 Explanation:  Used in the SHOW TRANSFER statement.

 Prologue file <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Number of retries <value> times

 Explanation:  Used in the SHOW TRANSFER statement.

 Number of retries <value> times

 Explanation:  Used in the SHOW TRANSFER statement.

 Schedule for transfer <text>:

 Explanation:  Used in the SHOW TRANSFER statement.

 Frequency Every day at <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Frequency Every <text>

 Explanation:  Used in the SHOW TRANSFER statement.

 Frequency Every <text> at UW:ZW:ZW.ZW

 Explanation:  Used in the SHOW TRANSFER statement.