Table 3-2: Client-Library error messages
Number
|
Text and explanation -
Error 1 through Error 117
|
Error 1
|
The information being retrieved will not fit in the buffer.
Explanation: The buffer size specified is too small.
Action: Change the application code to specify a larger buffer size.
|
Error 2
|
Memory allocation failure.
Explanation: CICS is running short on storage.
Action: Have the CICS system programmer increase the size of the
DSA or EDSA storage pools in the CICS start-up procedure.
|
Error 3
|
Parameter cannot be NULL. (e.g. invalid buffer address)
Explanation: The application passed an invalid buffer address of zero.
Action: Provide a valid buffer address.
|
Error 5
|
An illegal value given for parameter = action.
Explanation: The action code specified in a call contains an invalid value.
Action: Correct the application program to pass a valid value (for
example, CS_SET or CS_GET in
the ACTION parameter of the Client-Library routine).
|
Error 6
|
The maximum number of connections have already been opened.
Explanation: The maximum number of connections allowed for the program
was reached. The default is 25 connections.
Action: Increase the maximum number of connections by issuing a CTBCONFIG call
to increase the CS_MAX_CONNECT setting.
|
Error 10
|
Boolean values must be set to either CS_TRUE or CS_FALSE.
Explanation: An invalid value was specified for a Boolean argument; only
0 or 1 is valid.
Action: Correct the application program to specify a valid value for
the Boolean argument.
|
Error 14
|
Cannot set this property/capability.
Explanation: Some configuration and property values are read-only values
and cannot be set by an application.
Action: Remove the call to set a read-only value.
|
Error 16
|
This routine cannot be called after a command has been initiated to a Server.
Explanation: A Client Option application issues commands such as CTBPARAM and CTBCOMMAND while
it receives the results of a previous command being returned from
the server.
Action: Correct the application so that it does not send commands
while receiving results from the server.
|
Error 46
|
An illegal value was placed in the DATAFMT structure.
Explanation: An invalid or undefined value was placed in one of the DATAFMT
fields (for instance, FMT_TYPE, FMT_STATUS,
FMT_COUNT, FMT_NAMELEN, FMT_MAXLEN).
Action: Check DATAFMT and correct the invalid value.
|
Error 50
|
The connection is dead/crashed.
Explanation: The SNA session to the remote server crashed due to a network
outage, or the application running on the remote server abnormally
terminated.
Action: Determine the cause of the crash and either have the VTAM
operator restart the failing network connections or repair the server
application.
|
Error 53
|
Not enough memory was available to save messages. All messages stored previously have been cleared.
Explanation: The maximum number of error messages was reached (as specified
by the CS_MSGLIMIT value for CTBDIAG).
As new messages were added, the old ones were released.
Action: Issue CTBDIAG calls to retrieve and free
(CS_CLEAR option) error messages that are queued up.
|
Error 57
|
A result datatype cannot be bound to that host program variable type.
Explanation: An implicit conversion between the server datatype and the
datatype of the host program variable is not supported.
Action: Bind the result column or parameter to a host variable that
is compatible.
|
Error 60
|
Usage error. This routine has been called at an illegal time.
Explanation: A Client Option application cannot issue commands such as CTBPARAM and CTBCOMMAND when
it issued a previous command and is receiving the results of that
command from the server.
Action: Correct the application so that it does not send commands
while receiving results from the server.
|
Error 79
|
Bind of result set item resulted in overflow.
Explanation: This warning indicates that an overflow occurred when converting
a result set value to a program variable that is too small.
Action: Verify that the program variable size is correct.
|
Error 80
|
Bind of result set item resulted in underflow.
Explanation: This warning indicates that an underflow occurred when converting
a result set value to a program variable that is too large.
Action: Verify that the underflow value is correctly processed.
|
Error 81
|
Bind of result set item failed because illegal precision value specified.
Explanation: The precision value is outside the bounds supported by the
Client Option.
Action: Choose a smaller precision value. For additional information,
see the Mainframe Connect Client Option Programmers’s
Reference for the program language.
|
Error 82
|
Bind of result set item failed because illegal scale value was specified.
Explanation: The specified scale value is outside the bounds supported
by the Client Option.
Action: Choose a smaller scale value. For additional information,
see the Mainframe Connect Client Option Programmers’s
Reference for the program language.
|
Error 89
|
The data for a column is NULL but no indicator variable was available.
Explanation: A NULL value was received for a column or parameter that
was bound without a NULL indicator variable.
Action: Change the application to use NULL indicator variables.
|
Error 90
|
The data for a column was truncated but no indicator variable was available.
Explanation: No NULL indicator variable was defined for a column.
Action: If the truncated information is needed, define a NULL indicator
variable in the CTBBIND call.
|
Error 91
|
A bind was missing for a column.
Explanation: This warning indicates that any data for the unbound column
is discarded.
Action: Change the application to bind the data for that column, if
the data is needed.
|
Error 95
|
Fetched value was truncated.
Explanation: This is a warning message.
Action: Expand the size of the input buffer.
|
Error 110
|
The Conn Router Table has not been initialized.
Explanation: The start-up initialization for the Connection Router Table
was not performed.
Action: Run the SYMPINIT PLT/PI program, or run the SYMI
program after CICS is up, to initialize the Connection Router Table.
|
Error 111
|
The requested Server is not defined in the Conn Router Table.
Explanation: A configuration error has occurred.
Action: Use the Add option of the SYMS transaction
to add the server to the system.
|
Error 112
|
No connections were configured for the requested Server.
Explanation: A configuration error has occurred.
Action: Use the Add option of the SYMC transaction
to configure connections for the server.
|
Error 113
|
Temporary error: All connections to the requested server are currently in use.
Explanation: All the configured SNA connections to a server are in use.
Action: Increase the number of SNA connections to the designated
server. Also, check that there are no “hung” transactions
using connections to that server.
|
Error 114
|
Invalid context handle.
Explanation: An invalid context handle was used, or a previous CSBCTXALLOC failed.
Action: Fix the application program to use a valid handle.
|
Error 115
|
Invalid connection handle.
Explanation: An invalid connection handle was used, or a previous CTBCONALLOC failed.
Action: Fix the application program to use a valid handle.
|
Error 116
|
Invalid command handle.
Explanation: An invalid command handle was used, or a previous CTBCMDALLOC failed.
Action: Fix the application to use a valid handle.
|
Error 117
|
The operation requested is illegal on a client connection.
Explanation: The application tried to issue an Open Server command over
a client command handle.
Action: Correct the application program to use an Open Server TDPROC
handle.
|