ALLBASE/SQL Warning Messages (Continued) [ ALLBASE/SQL Message Manual ] MPE/iX 5.5 Documentation
ALLBASE/SQL Message Manual
ALLBASE/SQL Warning Messages (Continued)
10605 MESSAGE User's and DBE's languages are different.
(DBWARN 10605)
CAUSE The job control word NLUSERLANG and the language of
the DBEnvironment are different.
ACTION Set NLUSERLANG to the proper language, if using
native data.
----------------------------------------------------------------------------
10606 MESSAGE Native version of ALLBASE/SQL message catalog not
accessible. (DBWARN 10606)
CAUSE The native version of SQLCTxxx.PUB.SYS was not
found.
ACTION Install native message catalog, if required.
----------------------------------------------------------------------------
10607 MESSAGE Program name exceeds maximum module name length.
Truncated to 20 bytes. (DBWARN 10607)
CAUSE The program name is used as the module name when
none is specified in the program invocation line.
A program name was specified which is longer than
the maximum allowed module name length of 20 bytes.
ACTION Modify the source file to specify a program name
with a length of 20 bytes or less.
----------------------------------------------------------------------------
10608 MESSAGE ALLBASE/SQL preprocessor warning. (DBWARN 10608)
CAUSE A warning condition was detected by the
preprocessor. Additional warning messages will be
returned.
ACTION Refer to the cause and action of the additional
warning messages.
----------------------------------------------------------------------------
10609 MESSAGE ALLBASE/SQL statement parser warning. (DBWARN
10609)
CAUSE A warning condition was detected by the statement
parser. Additional warning messages will be
returned.
ACTION Refer to the cause and action of the additional
warning messages.
----------------------------------------------------------------------------
10610 MESSAGE ALLBASE/SQL query processor warning. (DBWARN
10610)
CAUSE A warning condition was detected by the query
processor. Additional warning messages will be
returned.
ACTION Refer to the cause and action of the additional
warning messages.
----------------------------------------------------------------------------
10611 MESSAGE Cannot obtain user's language. Default language
! assumed. (DBWARN 10611)
CAUSE The NLUSERLANG job control word is set to an
unrecognized language.
ACTION Set NLUSERLANG to a supported language.
----------------------------------------------------------------------------
10612 MESSAGE Native version of ALLBASE/SQL message catalog not
accessible. (DBWARN 10612)
CAUSE The native version of the SQLCTxxx.PUB.SYS message
catalog was not found.
ACTION Install the native message catalog.
----------------------------------------------------------------------------
10613 MESSAGE User's and DBE's languages are different.
(DBWARN 10613)
CAUSE The NLUSERLANG job control word and the language of
the DBEnvironment are different.
ACTION Set NLUSERLANG to the proper language.
----------------------------------------------------------------------------
10614 MESSAGE Not enough space to return parse information.
(DBWARN 10614)
CAUSE The buffer space passed to hold the returned parse
information was not sufficient.
ACTION Increase the buffer space.
----------------------------------------------------------------------------
[REV BEG]
10621 MESSAGE ***REDEFINES clause: Non-standard host variable
declaration. (DBWARN 10621)
CAUSE A possible cause is that the REDEFINE clause was
used.
ACTION No action required. Only elementary level items
are allowed in ALLBASE/SQL calls. In order to pass
an item with subitems in the COBOL preprocessor,
you can use a REDEFINE clause. However, you will
receive a warning because you are using a
non-standard host variable declaration.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
10622 MESSAGE Cannot obtain user's language. Default language C
assumed. (DBWARN 10622)
CAUSE The user's language is not found.
ACTION Check the native language parameters.
[REV END]
----------------------------------------------------------------------------
10700 MESSAGE Filler added to adjust for odd-byte field.
(DBWARN 10700)
CAUSE The preprocessor generated in the preprocessor
output file a one-byte filler character for an
odd-byte host variable declaration to ensure that
the data is aligned on word boundaries.
ACTION No action is necessary. The preprocessor inserted
the required one-byte filler character in the
preprocessor output file.
----------------------------------------------------------------------------
10701 MESSAGE Maximum COBOL work length exceeded. Truncated to
30 bytes. (DBWARN 10701)
CAUSE A word appears in the COBOL source file which is
longer than the maximum allowed length of 30 bytes.
ACTION Modify the source file to shorten the word to a
length of 30 bytes or less.
----------------------------------------------------------------------------
10750 MESSAGE 'INCLUDE SQLCA' is not declared for embedded SQL
statement. (DBWARN 10750)
CAUSE You did not include an SQLCA common area in your
program.
ACTION Modify the source file specifying EXEC SQL INCLUDE
SQLCA and re-preprocess your program.
----------------------------------------------------------------------------
10979 MESSAGE ALLBASE/SQL query processor error. (DBWARN
10979)
CAUSE An error condition was detected by the query
processor. Additional error messages will be
returned.
ACTION Refer to the cause and action of the additional
error messages.
----------------------------------------------------------------------------
10980 MESSAGE Syntax check only due to severe ALLBASE/SQL query
processor error. (DBWARN 10980)
CAUSE An unrecoverable error condition was detected by
the query processor. Only the syntax of the SQL
statement was verified. Validation of the SQL
statement was not performed. Additional error
messages will be returned.
ACTION Refer to the cause and action of the additional
error messages.
----------------------------------------------------------------------------
13026 MESSAGE Missing log files from log file list. (DBWARN
13026)
CAUSE WRAPDBE determined that log files were missing from
the log file list by checking the log sequence
numbers. The log file names can be entered in any
order; as long as there is a correct and continuous
sequence; WRAPDBE puts them in the correct order.
ACTION Check the log sequence numbers that were assigned
on the original DBEnvironment with the SQLUtil
SHOWLOG command to determine if all log files exist
in the target area.
----------------------------------------------------------------------------
[REV BEG]
13343 MESSAGE Consistency point may not be exactly enforced by
DBCORE. (DBWARN 13343)
CAUSE DBCORE is adjusting the consistency point.
ACTION No action required.
[REV END]
----------------------------------------------------------------------------
20010 MESSAGE Local catalog is inaccessible. Default catalog
in use. (DBWARN 20010)
CAUSE The ALLBASE/SQL message catalog corresponding to
your language cannot be accessed, probably because
it does not exist.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
20011 MESSAGE *** Bad JOB CONTROL WORD MIGLOGSZ. Default size
used. (DBWARN 20011)
CAUSE The job control word MIGLOGSZ has been set to an
integer value that is less than 400 (the default
log size)
ACTION Issue the SETJCW MIGLOGSZ again, but specify a log
file size that is no less than 400.
----------------------------------------------------------------------------
20014 MESSAGE Cannot verify ALLBASE/SQL license. Assuming
IMAGE/SQL
(! !) (DBWARN 20014)
CAUSE An error occurred during processing that determines
whether or not your system is licensed to use
ALLBASE/SQL.
ACTION If you have not purchased a license to use
ALLBASE/SQL, no action is necessary. Otherwise,
record as much information as possible and contact
your HP Service Representative or Response Center,
because restrictions imposed by IMAGE/SQL are
currently in effect for your DBEnvironment.
----------------------------------------------------------------------------
20300 MESSAGE WARNING - No DBEnvironment has been referenced
yet. (DBWARN 20300).
CAUSE Either the CREATE DBEFILE or the ADD DBEFILE
statement was issued before a DBEnvironment had
been mentioned in a command.
ACTION Use either the SHOW 'DBEnvironmentName' VERSION
command or the PREVIEW command to indicate to
SQLMigrate which DBEnvironment should be used for
this command.
----------------------------------------------------------------------------
20550 MESSAGE WARNING - Before continuing, please verify that a
complete backup of the DBEnvironment exists.
(DBWARN 20550)
CAUSE This warning is issued to insure that you do not
accidentally corrupt a DBEnvironment when using
SQLMigrate and you will be unable to recover your
data. If an unexpected error is encountered during
the MIGRATE or PREVIEW command, it is critical that
a backup of the DBEnvironment be available.
ACTION If you have not made a complete backup of the
DBEnvironment, type No at the prompt to prevent
SQLMigrate from continuing. Make a full backup of
the DBEnvironment, and then issue the MIGRATE or
PREVIEW command again.
----------------------------------------------------------------------------
20570 MESSAGE WARNING - Table !.! contained the following
columns which are not supported under the target
release of ALLBASE/SQL. (DBWARN 20570)
CAUSE A backward migration was in progress when this
message was issued. Column types that were only
supported under the newer release of ALLBASE/SQL
were present in the user table mentioned in the
warning. The table was dropped during the
migration.
ACTION If you need to recover the table, the backup
version of the DBEnvironment must be restored. The
offending columns must be eliminated or modified to
be of types supported by the target version before
a migration is attempted again.
----------------------------------------------------------------------------
20580 MESSAGE WARNING - Views and stored sections created under
later releases of ALLBASE/SQL may not function
correctly under the target version of ALLBASE/SQL.
(DBWARN 20580)
CAUSE This message is issued as a warning whenever a
backward migration occurs.
ACTION Drop all views created under later releases, and
recreate them. Also drop all stored sections
created under later releases, and either:
INSTALL backup installable module files that were
created under the target version of ALLBASE/SQL,
or
preprocess programs again to obtain stored sections
that are compatible with the target version of
ALLBASE/SQL.
----------------------------------------------------------------------------
20650 MESSAGE WARNING - Table !.! has been created using the
HASH option, which is not supported under the
target version of ALLBASE/SQL (DBWARN 20650). This
table is being dropped.
CAUSE A backward migration was in progress when this
message was issued. User data which takes
advantage of functionality that is not present in
the target release has been detected.
ACTION If you need to recover the table, the backup
version of the DBEnvironment must be restored. If
you need to transfer this data to the target
release, use the ISQL UNLOAD EXTERNAL command.
----------------------------------------------------------------------------
20660 MESSAGE WARNING - Table !.! has been created using
INTEGRITY CONSTRAINTS, which is not supported under
the target version of ALLBASE/SQL (DBWARN 20660).
This table is being dropped.
CAUSE A backward migration was in progress when this
message was issued. User data which takes
advantage of functionality that is not present in
the target release has been detected.
ACTION If you need to recover the table, the backup
version of the DBEnvironment must be restored. If
you need to transfer this data to the target
release, use the ISQL UNLOAD EXTERNAL command.
----------------------------------------------------------------------------
20670 MESSAGE WARNING - Table !.! has been created using
DEFAULT column values, which is not supported under
the target version of ALLBASE/SQL (DBWARN 20670).
This table is being dropped.
CAUSE A backward migration was in progress when this
message was issued. User data which takes
advantage of functionality that is not present in
the target release has been detected.
ACTION If you need to recover the table, the backup
version of the DBEnvironment must be restored. If
you need to transfer this data to the target
release, use the ISQL UNLOAD EXTERNAL command.
----------------------------------------------------------------------------
20680 MESSAGE WARNING - TEMPSPACE ! has been created using the
CREATE TEMPSPACE statement, which is not supported
under the target version of ALLBASE/SQL (DBWARN
20680). This TEMPSPACE is being dropped.
CAUSE A backward migration was in progress when this
message was issued. User data which takes
advantage of functionality that is not present in
the target release has been detected.
ACTION No action is necessary.
----------------------------------------------------------------------------
MPE/iX 5.5 Documentation