HP 3000 Manuals HP 3000 Manuals
Appendix A Error Messages From the PC Client
Errors from ALLBASE/SQL are followed by DBERR or DBWARN and a number.
Some of these ALLBASE/SQL messages contain exclamation points (!), which
are replaced by more specific information (such as a number, file name,
or subsytem name) when the condition occurs in processing. These error
messages can be found in the ALLBASE/SQL Message Manual.
Errors generated by Gupta are listed in the ERROR.SQL file. This file
was copied to your PC when you installed PC API.
The error messages listed in this appendix are detected on the PC client
only.
20002 MESSAGE Expected / delimiter not found.
CAUSE The connection logon is missing a forward slash.
ACTION Check the syntax in the SQL.INI file or direct
logon.
20003 MESSAGE Session or user name ! in the logon is invalid.
CAUSE A user or MPE session name in the SQL.INI file or
direct logon has incorrect syntax.
ACTION Make sure that the user and session name are
alphanumeric.
20004 MESSAGE Group name ! in the logon is invalid.
CAUSE An MPE group name in the SQL.INI file or direct
logon has incorrect syntax.
ACTION Make sure that the group name is alphanumeric.
20005 MESSAGE Account name ! in the logon is invalid.
CAUSE An MPE account name in the SQL.INI file or direct
logon has incorrect syntax.
ACTION Make sure that the account name is alphanumeric.
20006 MESSAGE Password ! in the logon is invalid.
CAUSE A password in the SQL.INI file or direct logon has
incorrect syntax.
ACTION Make sure that the password is alphanumeric.
20007 MESSAGE The DBE name ! in the logon is invalid.
CAUSE A DBEnvironment name in the SQL.INI file or direct
logon has incorrect syntax.
ACTION Make sure that the DBEnvironment name is
alphanumeric.
20010 MESSAGE Expected a period (.) found ! instead.
CAUSE A name should have been delimited by a period.
ACTION Check the syntax in the SQL.INI file or direct
logon.
20020 MESSAGE Zero length string was passed as a parameter.
CAUSE A NULL string was unexpectedly found. The string
could have been the SQL statement or write bind
value.
ACTION Check the size of input strings passed to PC API.
20021 MESSAGE Syntax error in the SQL statement.
CAUSE The client detected a parse error in the SQL
statement.
ACTION Check the syntax of the SQL statement.
20025 MESSAGE Invalid data length.
CAUSE The client detected an error in an input parameter.
ACTION Check the length of input values, such as the
connect string or input bind value.
20027 MESSAGE Bind variable ! was not found in the current
statement.
CAUSE The bind variable was expected to be specified in
the SQL statement being executed.
ACTION Check the bind variable syntax of the SQL
statement.
20028 MESSAGE Column Number ! is not available.
CAUSE A column number input parameter is invalid. The
error is detected during a Fetch or Read Long.
ACTION Contact your HP Service Representative or Response
Center.
20031 MESSAGE Column ! is not the correct type to be bound as a
long.
CAUSE The column datatype must be CHAR or VARCHAR when
binding to a Gupta Long data type.
ACTION Check the table definition for the correct data
types.
20032 MESSAGE Previous long operation not ended with SQLELO.
CAUSE An End Long request must complete a Gupta Long
command.
ACTION Check the SQLBase C Application Programming
Interface Reference Manual for a discussion on Long
operations, or contact your HP Service
Representative or Response Center.
20033 MESSAGE Duplicate Name !.
CAUSE A name duplicates another already defined name.
The previously defined name could be a cursor name.
ACTION Check the SQLBase C Application Programming
Interface Reference Manual for discussion of cursor
names, or contact your HP Service Representative or
Response Center.
20034 MESSAGE Invalid cursor name !.
CAUSE The cursor name has a syntax error.
ACTION Check the syntax of the cursor name. It must be
alphanumeric.
20035 MESSAGE Must execute the statement before fetching.
CAUSE A statement was not executed before a fetch request
was made.
ACTION Contact your HP Service Representative or Response
Center.
20036 MESSAGE The statement is not a Select.
CAUSE A Select type of operation was requested for a
non-Select statement.
ACTION Contact your HP Service Representative or Response
Center.
20039 MESSAGE Fetch must be executed before this call.
CAUSE A Long operation cannot be made until the data is
fetched.
ACTION Fetch the data before executing this call.
20040 MESSAGE Column ! is not an ALLBASE VARCHAR or CHAR field.
CAUSE The column must be a VARCHAR or CHAR field in a
Long operation.
ACTION Change the column types to be compatible.
20041 MESSAGE Column ! in the SET list does not exist.
CAUSE The UPDATE statement SETs a column name that
doesn't exist.
ACTION Check the definition of the table(s) specified in
the UPDATE statement.
20044 MESSAGE No current transaction due to sqlcmt or sqlrbk.
CAUSE You cannot execute or fetch if there is no current
transaction.
ACTION Start a transaction before the execute or fetch.
20045 MESSAGE Information Buffer in SQLGET cannot be NULL.
CAUSE A Get Parameter value could not be returned to the
caller.
ACTION Contact your HP Service Representative or Response
Center.
20048 MESSAGE Attempted to seek beyond long column end.
CAUSE The requested seek position is greater than the
size of the column.
ACTION Change the seek position so that it is not greater
than the size of the column.
20049 MESSAGE Non-null bind value expected.
CAUSE An attempt was made to bind a non-null value to a
column which doesn't allow nulls.
ACTION Check the table definition or bind value.
20055 MESSAGE REMOTEDBNAME and/or REMOTEUSER not in SQL.INI.
CAUSE The mpedbname and/or the mpeuser specified in a
non-direct logon was not defined in the SQL.INI
file.
ACTION Check the SQL.INI file for the correct definition.
20064 MESSAGE Error with direct logon.
CAUSE A syntax error was detected in the direct logon
string.
ACTION Check the syntax of the direct logon string.
20100 MESSAGE Unable to lock local memory.
CAUSE An error was detected while locking local memory.
ACTION Retry the operation or try to free more memory.
20101 MESSAGE Unable to unlock local memory.
CAUSE An error was detected while unlocking local memory.
ACTION Retry the operation.
20102 MESSAGE Unable to allocate local memory.
CAUSE An error was detected while allocating local
memory.
ACTION Retry the operation or try to free more memory.
20103 MESSAGE Unable to lock global memory.
CAUSE An error was detected while locking global memory.
ACTION Retry the operation or try to free more memory.
20104 MESSAGE Unable to allocate global memory.
CAUSE An error was detected while allocating global
memory.
ACTION Retry the operation or try to free more memory.
20105 MESSAGE Unable to reallocate global memory.
CAUSE An error was detected while reallocating global
memory.
ACTION Retry the operation or try to free more memory.
20106 MESSAGE Unable to free global memory.
CAUSE An error was detected while attempting to free
global memory.
ACTION Retry the operation.
20107 MESSAGE Unable to free local memory.
CAUSE An error was detected while attempting to free
local memory.
ACTION Retry the operation.
20108 MESSAGE Unable to reallocate local memory.
CAUSE An error was detected while reallocating local
memory.
ACTION Try to free more memory, or contact your HP Service
Representative or Response Center
20112 MESSAGE INTERNAL ERROR: Missing outfmtarray in cursor.
CAUSE Format array was lost in the Describe operation.
ACTION Contact your HP Service Representative or Response
Center.
20113 MESSAGE All variables must be bound before executed.
CAUSE The SQL statement had bind variables, not all of
which were bound with input data.
ACTION Check that all the bind variables were bound with
input data.
20115 MESSAGE No named cursor.
CAUSE The cursor specified in the SQL statement is not
defined.
ACTION Check the cursor specification in the SQL
statement. Check that the cursor name is the same
name specified in the statement.
20116 MESSAGE Can't bind a long data type.
CAUSE Write Long failed because there was a bind error.
ACTION Check the Gupta C/API manual for discussion on
binding, or contact your HP Service Representative
or Response Center.
20119 MESSAGE Connection list full: Too many connects.
CAUSE Exceeded maximum number of connections.
ACTION Disconnect one connection and retry.
20120 MESSAGE Cursor list full: Too many open cursors.
CAUSE Exceeded maximum number of cursors.
ACTION Close one of the cursors and retry.
20200 MESSAGE INTERNAL ERROR.
CAUSE Unknown.
ACTION Contact your HP Service Representative or Response
Center.
20301 MESSAGE Netware SPX not installed.
CAUSE Netware SPX is not installed on the client.
ACTION Install Netware SPX, or check the network
specification in the connection request.
20302 MESSAGE No file found for playback.
CAUSE Playback could not find the input file.
ACTION Contact your HP Service Representative or Response
Center.
20303 MESSAGE Error writing to a log file.
CAUSE An error was detected while writing to the datacomm
trace file.
ACTION Retry and if still fails, try deleting the file
before retrying.
20304 MESSAGE Unexpected EOF on playback file.
CAUSE Playback could not find the input file.
ACTION Contact your HP Service Representative or Response
Center.
20305 MESSAGE Playback file has bad header info.
CAUSE Invalid data was found in the playback file.
ACTION Contact your HP Service Representative or Response
Center.
20306 MESSAGE Network software not loaded.
CAUSE The system is unable to locate network software.
ACTION Follow these steps:
* Make sure that the network is running.
* Check that the path statement in the
AUTOEXEC.BAT file shows the correct path for
network software.
* Verify that your network software is the
correct version.
20307 MESSAGE Unsupported conversion. Need Roman8 or ANSI.
CAUSE An invalid conversion option was used in the
connection string.
ACTION Be sure to use the 'an' convertion option for the
ANSI character set.
20309 MESSAGE Unsupported dctype. Need Sockets, Netware or IPC.
CAUSE The connection string had an unrecognizable
datacomm type.
ACTION Check the connection string for correct syntax.
20310 MESSAGE Received packet is bigger than expected.
CAUSE The server sent more data than the client expected.
ACTION Contact your HP Service Representative or Response
Center.
20312 MESSAGE Logon attempt failed. !
CAUSE Connection failed.
ACTION Look at the expanded error text for more
information.
20313 MESSAGE Connection error from the server: !.
CAUSE The server detected a connection error.
ACTION Look at the expanded error text for more
information.
20314 MESSAGE Virtual Circuit not allocated.
CAUSE The virtual circuit was not created or was lost.
ACTION Contact your HP Service Representative or Response
Center.
20317 MESSAGE Unsupported data type conversion.
CAUSE Client could not convert a data type to the type
specified.
ACTION Conversions are made only on CHAR and VARCHAR data
types for bind variables.
20318 MESSAGE User Timeout value reached.
CAUSE Client hung on a Send or Receive from the network.
ACTION Check connection on the server for any errors, or
Contact your HP Service Representative or Response
Center.
20319 MESSAGE Received packet is smaller than expected.
CAUSE Client received less data from the Server than
expected.
ACTION Contact your HP Service Representative or Response
Center.
20334 MESSAGE Netware data communications error !.
CAUSE An error was detected by Netware.
ACTION Look at the expanded error text for error
information.
20340 MESSAGE NetIPC data communications error !.
CAUSE An error was detected by NetIPC.
ACTION Look at the expanded error text for error
information.
20361 MESSAGE No match of server name !.
CAUSE The server name specified in the connection string
could not be found on the network. The SQL.INI
file contains faulty information, or the wrong
SQL.INI file has been accessed.
ACTION You can take the following actions:
* Check the connection string for the correct
server name.
* Check the network node specifications on the
client.
* Check to see if you have a duplicate SQL.INI
file in your directory structure. You
should only have one on the PC. If you have
a duplicate, rename it.
* Check the path in the AUTOEXEC.BAT file. Is
the path set correctly?
* When PC API is initialized, it loads the
SQL.INI file information. If you change the
SQL.INI file while PC API is running, you
must close and restart it to activate your
changes. To close the PC API, disconnect
all logons, single-click on the PC API icon,
and select Close.
20362 MESSAGE PC Sockets error: !2. (PCSockets !1)
CAUSE Sockets detected an error.
ACTION Look at the expanded error text and refer to the
Sockets Manual.
20602 MESSAGE Missing = sign in the [ALLBASE] section
definition.
CAUSE The mpedbname or mpeuser specification in the
SQL.INI file needs an equal sign.
ACTION Correct the syntax in the SQL.INI file.
20605 MESSAGE Missing ',' in the [ALLBASE] section definition.
CAUSE The mpedbname or mpeuser specification in the
SQL.INI file or direct logon needs a comma.
ACTION Correct the syntax in the SQL.INI file or direct
logon.