Ch 2. ALLBASE/SQL Warning Messages [ ALLBASE/SQL Message Manual ] MPE/iX 5.5 Documentation
ALLBASE/SQL Message Manual
Chapter 2 ALLBASE/SQL Warning Messages
ALLBASE/SQL Warning Messages
1 MESSAGE Output will be truncated. (DBWARN 1)
CAUSE The SELECT statement generated rows that are longer
than the size specified by the PAGEWIDTH option of
the SET command. The pagewidth may be set to a
maximum of 254 bytes.
ACTION Increase the pagewidth value using the ISQL SET
command.
----------------------------------------------------------------------------
2 MESSAGE File '!' already exists. Next SELECT will
overwrite. (DBWARN 2)
CAUSE You have specified a file name that already exists
as the output file for the results of a SELECT.
ACTION No action is necessary if you want to overwrite the
existing file. Specify another output file name
using the OUTPUT option of the ISQL SET command if
you want output to go to a different file.
----------------------------------------------------------------------------
3 MESSAGE Column name ! truncated to ! bytes. (DBWARN 3)
CAUSE A column name specified in the ISQL INPUT command
was greater than 20 bytes. This probably occurred
because you did not leave a space between column
names. If the bytes which remained after the
truncation formed an existing column name, the
command was executed for that column.
ACTION Delete any rows that were incorrectly input. Issue
the INPUT command again, separating the column
names with spaces.
----------------------------------------------------------------------------
4 MESSAGE Parameter substitution caused overflow - command
truncated. (DBWARN 4)
CAUSE Substitution of parameter values into the command
caused the command length to exceed 2048 bytes,
necessitating truncation.
ACTION Try to rewrite the command so that the command
length after parameter substitution will be no
greater than 2048 bytes.
----------------------------------------------------------------------------
5 MESSAGE BULK not allowed interactively - ignored.
(DBWARN 5)
CAUSE You issued a BULK SELECT or BULK FETCH option while
in ISQL.
ACTION Any SELECT performed in ISQL is automatically
treated as a BULK SELECT. BULK is an option for
programming with SQL only. Refer to the
ALLBASE/SQL Reference Manual for additional
information.
----------------------------------------------------------------------------
6 MESSAGE Transaction terminated. (DBWARN 6)
CAUSE EOF was reached on input file.
ACTION SQLCore automatically rolled back the transaction.
No action is necessary.
----------------------------------------------------------------------------
7 MESSAGE Commands after START ignored. (DBWARN 7)
CAUSE You may not have any additional commands on the
command line after a START command.
ACTION Refer to the ALLBASE/SQL Reference Manual for more
information.
----------------------------------------------------------------------------
8 MESSAGE Numeric field error on line !, column !. (DBWARN
8)
CAUSE The line number specified contains non-numeric data
in the column indicated. The LOAD EXTERNAL command
continues executing and loads a 0 value for that
column.
ACTION Refer to the ISQL Reference Manual for ALLBASE/SQL
and IMAGE/SQL for additional information on the
LOAD EXTERNAL command.
----------------------------------------------------------------------------
9 MESSAGE Entire command has been deleted. (DBWARN 9)
CAUSE You deleted the entire command using the REDO
command.
ACTION No action is necessary.
----------------------------------------------------------------------------
10 MESSAGE Load file is empty. (DBWARN 10)
CAUSE The file that you named in the LOAD EXTERNAL
command is empty. No rows were processed.
ACTION No action is necessary.
----------------------------------------------------------------------------
11 MESSAGE LOAD command stopped because of error. (DBWARN
11)
CAUSE An INTERNAL load could not be continued due to
another error. An additional message will be
returned.
ACTION Refer to the cause and action of the additional
message.
----------------------------------------------------------------------------
12 MESSAGE Starting row is beyond end of load file. (DBWARN
12)
CAUSE The starting row number specified in the LOAD
PARTIAL command was beyond the last line of the
file. No rows were loaded.
ACTION Issue the LOAD command again, specifying an
appropriate starting row.
----------------------------------------------------------------------------
13 MESSAGE Number of rows specified exceeds number in load
file. (DBWARN 13)
CAUSE The number of rows specified in the LOAD PARTIAL
command was greater than the number of rows between
the starting row and the end of the file.
ACTION No action is necessary. All qualifying rows, from
the starting row to the end of the file, were
loaded.
----------------------------------------------------------------------------
14 MESSAGE User language and DBE language differ. (DBWARN
14)
CAUSE You started or connected to a DBEnvironment with a
language other than your current language.
ACTION Exit ISQL. Set your NLUSERLANG job control word and
invoke ISQL.
----------------------------------------------------------------------------
15 MESSAGE Local catalog is inaccessible. Default catalog
in use. (DBWARN 15)
CAUSE The ALLBASE/SQL message catalog corresponding to
your language cannot be accessed, probably because
it does not exist.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
16 MESSAGE Unable to load all local response options.
(DBWARN 16)
CAUSE One or more of the local response options was
missing from the message catalog or contained
invalid data.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
17 MESSAGE Local response options are not unique. (DBWARN
17)
CAUSE The local response options in the message catalog
are not unique.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
18 MESSAGE Field boundaries specified do not coincide with
character boundaries. (DBWARN 18)
CAUSE The byte at a starting location specified in the
LOAD command is the second byte of a two-byte
character, or the last byte of a field is the first
byte of a two-byte character.
ACTION Delete the rows loaded. Issue the LOAD command
again, specifying field boundaries that coincide
with character boundaries.
----------------------------------------------------------------------------
19 MESSAGE Unable to upshift native language string.
(DBWARN 19)
CAUSE ISQL was unable to upshift a character string,
probably because the string contains one or more
invalid bytes.
ACTION Issue your command again, specifying valid input.
----------------------------------------------------------------------------
20 MESSAGE Unable to split string into lines. (DBWARN 20)
CAUSE ISQL was unable to split a character string into
lines, probably because the string contains one or
more invalid bytes.
ACTION Issue your command again, specifying valid input.
----------------------------------------------------------------------------
21 MESSAGE Unable to trim trailing blanks from multi-byte
native language string. (DBWARN 21)
CAUSE ISQL was unable to trim trailing blanks from a
character string, probably because the string
contains one or more invalid bytes.
ACTION Issue your command again, specifying valid input.
----------------------------------------------------------------------------
22 MESSAGE Unable to truncate multi-byte native language
string. (DBWARN 22)
CAUSE ISQL was unable to truncate a character string,
probably because the string contains one or more
invalid bytes.
ACTION Issue your command again, specifying valid input.
----------------------------------------------------------------------------
23 MESSAGE Unable to obtain user language. Default language
NATIVE-3000 assumed. (DBWARN 23)
CAUSE Your NLUSERLANG job control word is set to a
language that is not configured, or the support
files for your language are missing.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
24 MESSAGE No language set. Default language n-computer
assumed. (DBWARN 24)
CAUSE Your NLUSERLANG job control word is not set.
ACTION Set your NLUSERLANG job control word if desired.
----------------------------------------------------------------------------
25 MESSAGE Local welcome file is inaccessible. Default file
in use. (DBWARN 25)
CAUSE The ISQL welcome file corresponding to your
language cannot be accessed, probably because it
does not exist.
ACTION Contact your system administrator.
----------------------------------------------------------------------------
232 MESSAGE ! conversion error on line !, column !. (DBWARN
232)
CAUSE There is a problem converting Date, Time, DateTime,
or Interval field to internal format when trying to
load the data from an external data file. The
error messages following this one will give more
specific information on the problem.
ACTION Check the load information specified for this field
(start position, length, date/time/interval field
format) and the format of the data value for
possible problems. Correct problems and redo LOAD
operation.
----------------------------------------------------------------------------
233 MESSAGE Default format not used for ! field, column !.
(DBWARN 233)
CAUSE You did not use the default format for a Date,
Time, DateTime or Interval field in the load
description file.
ACTION Modify the format in the descriptor file. Make
sure the data is in the default format and redo the
LOAD operation. Refer to the ALLBASE/ISQL
Reference Manual for format specifications.
----------------------------------------------------------------------------
234 MESSAGE Unable to convert ! value to a displayable
format. (DBWARN 234)
CAUSE Unable to convert a Date, Time, DateTime or
Interval value to a value that can be stored in the
data file. This was probably due to a bad format
or length specified for the field.
ACTION Check the unload format and length given for this
field. Correct any problems and redo the UNLOAD
operation.
----------------------------------------------------------------------------
235 MESSAGE Only first ! rows can be displayed. (DBWARN 235)
CAUSE More rows qualified for the SELECT statement than
can be viewed through ISQL.
ACTION If all the rows of data need to be viewed, use the
UNLOAD EXTERNAL command to unload the data to an
ASCII file.
----------------------------------------------------------------------------
236 MESSAGE *WARNING*: DATA NOT COMPLETE - FIRST ! ROWS
DISPLAYED. (DBWARN 236)
CAUSE This message is displayed on the last line of the
outfile when an outfile is specified with the
OUTPUT option of the ISQL SET command and more rows
qualify for the SELECT than can be viewed within
ISQL. The outfile will hold all the rows that can
be viewed within ISQL.
ACTION If all the rows of data need to be viewed, use the
UNLOAD EXTERNAL command to unload the data to an
ASCII file.
----------------------------------------------------------------------------
302 MESSAGE File Device Full. (DBWARN 302)
CAUSE Your storage medium (tape or disk) is full.
ACTION If your storage is on tape, mount another tape. If
your storage is on disk, exit, clean up the file
system, and try again. If the problem persists,
contact the system administrator.
----------------------------------------------------------------------------
502 MESSAGE Nothing left to audit. (DBWARN 502)
CAUSE This warning is returned if SQLAudit determines
that there is nothing left to audit in the
DBEnvironment log files. This usually is the case
if there have been no new transactions committed
between the time the beginning audit point was
defined and the ending audit point was defined.
ACTION This is not a real error, but you should check to
make sure the partitions that have been supplied to
SQLAudit include all partitions you wish to see
transactions for.
----------------------------------------------------------------------------
506 MESSAGE Partition ! has no committed transactions.
(DBWARN 506)
CAUSE The partition being audited has no committed
transactions. This basically means that no
committed transactions have touched data belonging
to the specified partition.
ACTION No action required except to make sure the
partition was intended to be audited.
----------------------------------------------------------------------------
522 MESSAGE Duplicate Partition Number entered. Ignored.
(DBWARN 522)
CAUSE The same partition was entered previously.
ACTION No action necessary since the duplicate partition
is ignored.
----------------------------------------------------------------------------
MPE/iX 5.5 Documentation