Codes returned to Client-Library functions are marked with
an asterisk.
One or more parameters passed on an API call are null and should not be.
A rollback was successfully performed.
TDYNAMIC: The size of the buffer is greater than the dynamic SQL-type field being retrieved.
TDYNAMIC: The size of the buffer is too small to return a dynamic SQL-type field.
The buffer is too small. The information being retrieved cannot fit in the buffer.
The operation was canceled. The remote partner issued a cancel. The current operation failed.
This code is also returned to the Client-Library function CTBDESCRIBE.
The transaction can only retrieve this value; it cannot set the value of this property.
This code is also returned to the Client-Library functions CTBCMDPROPS and CTBCONPROPS.
Gateway-Library found the double-byte character set specified by the client, but the corresponding double-byte module was not loaded at the mainframe.
This code is returned to TDACCEPT when a client specifies a double-byte character set (for example, Shift-JIS) for which the associated translate module was not loaded or defined to the mainframe system.
If the TP system is CICS, this can mean that the translate module was not defined in RDO (or to the PPT table), or that it is not present in the LOADLIB.
The client’s character set was not found. A double-byte character set was specified as the default.
This code represents two problems:
The character set named in the client’s login packet was not found in the table of character set names.
This may indicate that the client did not specify the character set correctly (for example, the -J option in isql or the dbsetlcharset value in a DB-Library™ program is invalid).
The Server Option was customized to process single-byte character sets, but the default character set is double-byte.
This usually indicates that the customization settings are incorrect for kanji support.
The value of the ACTION parameter is invalid. It should be either TDS-GET or TDS-SET.
A command is in progress. The current function cannot be called after a command is sent to a server.
This function is returned to the Client-Library functions CTBCLOSE and CTBCMDDROP.
There are computes present for this transaction.
The connection abended. The client/server connection abnormally ended (for example, the LU 6.2 session crashed or the remote transaction abended).
This code can also be returned to the Client-Library function CTBRESULTS.
The connection closed. The remote partner closed (deallocated) the client/server connection.
This code can be returned to many Client-Library functions.
The customization module cannot be loaded. This module is necessary for Gateway-Library operation.
The Connection Router table cannot be loaded.
This function is returned to the Client-Library function CTBCONNECT.
The cursor is closed. You cannot fetch, update, or delete when the cursor is closed.
The cursor is deallocated. You cannot deallocate the same cursor more than once.
The cursor is declared. You cannot declare the same cursor more than once.
The cursor is already open. You cannot open the same cursor more than once.
A cursor must be declared before it can be opened.
The cursor is not found.
The cursor is not open. A cursor must be open before a fetch, close, delete, or update.
There are cursors present for this transaction.
An error occurred during conversion of datetime data.
This may be a result of trying to convert to short datetime (TDSDATETIME4) for a client using an early TDS version. TDS versions earlier than 4.2 do not support the short datetime datatype.
Gateway-Library could not find the double-byte character set specified in the client login packet.
This usually indicates that the client request specified an invalid character set in, for example, the -J option in isql or the dbsetlcharset value in a DB-Library program.
An error occurred in conversion of packed decimal data.
The client login packet did not specify a character set or the specified client character set could not be found, and Gateway-Library did not find the default. (This code is returned for single-byte character sets only.)
The network driver is invalid.
There is a duplicate column description. You attempted to describe the same column twice with a TDESCRIB statement. The operation failed.
There are dynamic SQL requests present for this transaction.
A dynamic SQL request is already allocated.
A dynamic SQL request is already prepared. You cannot prepare a dynamic SQL request that is already deallocated.
A dynamic SQL request is not found.
The dynamic SQL request ID length is greater than 255.
There is not a SQL statement associated with the dynamic SQL request.
A dynamic SQL request is not prepared.
The dynamic SQL output is already defined. You cannot define dynamic SQL output more than once.
The dynamic SQL parameters are already defined. You cannot define dynamic SQL parameters more than once.
There is no SQL statement associated with the dynamic SQL request.
The specified column number, transaction number, or parameter does not exist.
The maximum number of connections are already open.
An error occurred in conversion of float values.
The program version you are using is newer than the version of the Gateway-Library phase in use.
The application calls a Client-Library function that is not supported by the Client Option. Check the code to be sure all functions called are included in the appropriate Mainframe Connect Server Option Programmer’s Reference.
Gateway-Library crashed.
The DSA could not be obtained for the Gateway-Library.
This function is returned to the Client-Library functions CTBCONALLOC and CSBCTXALLOC.
SYGWCICS (the Gateway-Library phase) could not be loaded.
There was an illegal function. The operation failed.
This code can indicate that a client application is trying to use a Gateway-Library function that is not supported for clients (for example, TDSNDROW).
There is a server or client message associated with the results of the last request.
The action was not CS-GET or CS-SET.
This is an invalid Boolean value. Boolean values must be set to either CS-TRUE or CS-FALSE.
An invalid connection handle address was specified.
An invalid context handle address was specified.
A “closed” cursor command specified an invalid option.
The Gateway-Library transaction received a “closed” cursor command, but the value of the OPTION field of the TDS-CURDESC structure is invalid. Valid options are TDS-CUR-UNUSED and TDS-CUR-DEALLOC.
A declare cursor command has an invalid option specified.
The Gateway-Library transaction received a declare cursor command, but the value of the OPTION field of the TDS-CURDESC structure is invalid. Valid options are TDS-CUR-UNUSED and TDS-CUR-DEALLOC.
There was an illegal cursor declare option.
There was an illegal cursor information command.
There was an illegal cursor information status.
Illegal cursor open status.
The cursor command is not declare, open, fetch, delete, update, or close.
There was an invalid cursor state.
There was an illegal cursor update status.
The datatypes were incompatible. The source datatype cannot be converted into the requested result datatype.
There was an illegal datatype. A Sybase datatype supplied in the call is not supported, and the conversion cannot be done. The operation failed.
One or more values specified for fields in the DATAFMT structure are illegal.
This code is returned to Client-Library functions that use the Open Client DATAFMT structure: CTBBIND, CTBDESCRIBE, CTBPARARM, and CSBCONVERT.
There was an invalid dynamic SQL command. The dynamic SQL command must be prepare, exec, deallocate, descin, descount, or ack.
A dynamic SQL request is in invalid state.
There was an invalid status for a dynamic SQL request.
There was an invalid type for a dynamic SQL request.
There was an invalid padding option for a field.
The specified column or parameter number is greater than the system maximum. You can have as many columns per table result and parameters per RPC as Open Server allows.
There was an invalid IHANDLE specification. Error in specifying a value for the IHANDLE argument.
There was an incorrect length. The length specified in the xxx-LENGTH argument is too long.
There was an invalid name length. The length specified for the column, parameter, message, or server name is invalid.
This code is also returned to the Client-Library function CTBCONNECT (length of specified server name is invalid).
Invalid network protocol.
Invalid dynamic SQL operation.
There was an invalid parameter value. The value assigned to one or more of the arguments supplied in the call is not valid. The operation failed.
This code is also returned to many Client-Library functions.
Invalid precision value. The precision value specified during conversion of TDS-PACKED-DECIMAL data is invalid.
An invalid TDS protocol was received.
There was an invalid scale value. The scale value specified during conversion of TDS-PACKED-DECIMAL data is invalid.
There was an invalid status value. The value entered in the STATUS field is invalid.
An invalid TDS data stream length was received or an invalid TDS data stream length was specified.
There was an error in specifying a value for the TDPROC argument.
This code can also be returned to the Client-Library function CTBCANCEL.
There was an invalid terminator. The Terminator assigned to one or more parameters is not valid.
The specified variable address is invalid. No variable with the specified name exists. A NULL value was specified. The operation failed.
This code can also be returned to the Client-Library functions CTBBIND and CTBCONVERT.
An attempt to write to the log file failed.
The gatewayless login was rejected. Check validity of userid/password.
There was an error in the conversion of TDSMONEY-type data.
This might be a result of trying to convert to short money (TDSMONEY4) for a client using an early TDS version. TDS versions earlier than 4.2 do not support the short money datatype.
There was a memory shortage. Not enough memory is available to save messages. All messages stored previously were cleared.
This code can also be returned to the Client-Library function CTBDIAG.
The transaction has an outstanding server or client message.
No bind was issued. A bind is missing for the specified column.
The computed results are not supported by the Client Option.
This code is returned to the Client-Library functions CTBBIND and CTBDESCRIBE.
There is no cursor associated with the current transaction.
There is no dynamic SQL request associated with the current transaction.
There are no messages associated with the current transaction.
There is no null indicator. The data for the column is truncated, but no indicator is available.
There is no null indicator. The data for the column is NULL, but no indicator is available.
No incoming parameters are present. TDRCVPRM cannot retrieve a parameter because no additional parameters were received. The operation failed.
There are no more rows in the current result set.
There are no rows returned in the current result set. No rows were affected.
No incoming language string was present. TDRCVSQL cannot retrieve more text because no more text was accepted. The operation failed.
The Connection Router is not initialized.
This code is returned to the Client-Library function CTBCONNECT.
The function completed successfully.
Numeric/decimal conversion failed.
A parameter value was received. A parameter was received from the remote client. This value is returned to TDRESULT when a parameter is accepted by a server program and is ready to be retrieved.
The result set was purged. The transaction may have called a routine that expects the wrong communication state.
This code is returned to the Client-Library functions CTBBIND and CTBDESCRIBE.
TDRESULT indicated no more results. No more language text, RPC parameters, cancel requests, or messages were retrieved.
Results are in progress. More results are pending.
This code can be returned to CTBCMDDROP (cannot drop until all results process) and CTBEXIT (cannot close connection until all results process, unless OPTION is CS_FORCE_EXIT).
This code is returned to the Client-Library functions CTBCLOSE, CTBCONDROP, CTBCMDDROP and CTBEXIT.
A request route is not available. All paths are in use.
This code is returned to the Client-Library function CTBCONNECT.
The requested route is not defined to the Connection Router.
This code is returned to the Client-Library function CTBCONNECT.
Rows were returned in the current result set.
The requested server is not defined to the Connection Router.
This code is returned to the Client-Library function CTBCONNECT.
There is an error in the results sent by the server.
The host subsystem was unable to allocate enough memory for the control block that Gateway-Library was trying to create. The operation failed.
This code is returned to both Client-Library functions and Gateway-Library functions.
There is no scratch pad area designated for the IMS Conv Program.
A language request was received from a remote client. This value is returned to TDRESULT when a language string is accepted by a server program and is ready for retrieval.
A numeric or decimal-to-character conversion failed. The output length of the character string is too small.
No status returned from client. No RETURN-STATUS-NUMBER is available because the server did not yet send the status back to the client.
A status was returned from the client.
A sync point was successfully performed.
The application could not translate a character code or user-defined character.
This code is returned to the Client-Library function CTBFETCH.
An error occurred in the truncation of data value.
The data was truncated. The actual data length was longer than the maximum data length allotted for this data.
The function cannot be used in the current communication state. For example, your program tried to send a reply before it read in all of the client’s parameters. The application was still in RECEIVE state and could not send. The operation failed.
This code can be returned to both Gateway-Library and Client-Library functions.
