This table describes CSA and RSP programming error messages.
Table 2-1: CSA and RSP programming error messages
Number
|
Text and explanation -
001 through 085
|
|---|
001
|
TDINIT failed.
Explanation: The RPC issued an RPSETUP command and
the TDINIT failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
002
|
TDACCEPT failed.
Explanation: The RPC issued an RPSETUP command and
the TDACCEPT failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
003
|
TDRESULT failed.
Explanation: The RPC issued an RPSETUP command and
the TDRESULT failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
004
|
TDSNDDON(TDS_DONE_FINAL) failed.
Explanation: The RPC issued an RPDONE command and the TDSNDDON failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference.
|
005
|
TDFREE failed.
Explanation: The RPC issued an TDRESULT command and
the TDFREE failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
006
|
CSBCTXALLOC failed.
Explanation: The CSA issued an ATTACH command and the CSBCTXALLOC failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
007
|
CTBINIT failed.
Explanation: The CSA issued an ATTACH command and the CTBINIT failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
008
|
CTBCONALLOC failed.
Explanation: The CSA issued an ATTACH command and the CTBCONALLOC failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
009
|
CTBDIAG(CS_INIT) failed.
Explanation: The CSA issued an ATTACH command and the CTBDIAG failed
initializing message handling.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
010
|
error allocating message buffer.
Explanation: The CSA issued an ATTACH command, and
the support routines were unable to allocate memory for the message
buffer.
Action: Check your CICS region log to find the solutions.
|
011
|
CTBCONPROPS(CS_USERNAM) failed.
Explanation: The CSA issued an ATTACH command, and
the CTBCONPROPS failed to set the USERID in
the connection properties.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
012
|
CTBCONPROPS(CS_PASSWORD) failed
Explanation: The CSA issued an ATTACH command, and
the CTBCONPROPS failed to set the PASSWORD in
the connection properties.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
014
|
CTBCMDDROP failed.
Explanation: The CSA issued a DETACH command and the CTBCMDDROP failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
015
|
CTBCLOSE failed.
Explanation: The CSA issued a DETACH command and the CTBCCLOSE failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
016
|
CTBCONDROP failed.
Explanation: The CSA issued a DETACH command and the CTBCONDROP failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
017
|
CTBEXIT failed.
Explanation: The CSA issued a DETACH command and the CTBEXIT failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
019
|
CTBCMDALLOC failed.
Explanation: The CSA issued an REQEXEC command and
the CTBCMDALLOC failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
020
|
CTBCOMMAND failed.
Explanation: The CSA issued an REQEXEC command and
the CTBCOMMAND failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
021
|
CTBSEND failed.
Explanation: The CSA issued an REQEXEC command and
the CTBSEND failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
022
|
output pipe not allowed for a CSA.
Explanation: The CSA issued an OPENPIPE command for
an output pipe.
Action: Review your code and correct it. Output pipes are not permitted
for CSAs.
|
025
|
CTBFETCH CS_ROW_FAIL (CSA).
Explanation: The CSA issued a GETPIPE command and the CTBFETCH failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
027
|
PUTPIPE not allowed for CSA.
Explanation: The CSA issued a PUTPIPE command.
Action: Review your code and correct it. PUTPIPE,
a form of output pipe, is not permitted for CSAs.
|
029
|
CTBDIAG(CS_GET) failed.
Explanation: The CSA issued a GETMSG command, and the CTBDIAG failed
to get the messages.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible reasons.
|
030
|
TDSNDMSG failed.
Explanation: The RPC issued a STATUS command and the TDSNDMSG failed
to send the message to the client.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible reasons.
|
031
|
TDSNDDON(TDS_DONE_CONTINUE) failed.
Explanation: The RPC issued a STATUS command and the TDSNDDON failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
032
|
TDSNDMSG failed.
Explanation: The RPC issued a MESSAGE command and the TDSNDMSG failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
033
|
unable to allocate memory for SPAREA.
Explanation: The CSA or RSP issued a CSSETUP or RPSETUP command
and the subsystem was unable to allocate memory for the SPAREA.
Action: Check your CICS region log to find the causes.
|
034
|
CTBRESULTS command failed.
Explanation: The CSA issued a REQEXEC or RESCHECK command
and the previous command failed.
Action: No action is required.
|
035
|
CTBCMDDROP failed.
Explanation: The CSA issued a REQEXEC or RESCHECK command
and CTBCMDDROP failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
036
|
CTBRESULTS command failed.
Explanation: The CSA issued a REQEXEC or RESCHECK command
and CTBRESULTS failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
037
|
CTBDIAG(CS_STATUS) failed.
Explanation: The CSA issued a REQEXEC or RESCHECK command,
and CTBDIAG failed to retrieve the message status.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
038
|
CTBDIAG(CS_CLEAR) failed.
Explanation: The CSA issued a REQEXEC or RESCHECK command
and CTBDIAG failed to clear a message.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
040
|
CTBRESINFO(CS_NUMDATA) failed.
Explanation: The CSA issued an OPENPIPE command and CTBRESINFO failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
041
|
unable to allocate memory.
Explanation: The CSA issued an OPENPIPE command, and
the Server Option was unable to allocate the required memory in
the CICS subsystem.
Action: Check your CICS region log to find the causes.
|
042
|
unable to allocate memory.
Explanation: The CSA issued an OPENPIPE command, and
the Server Option was unable to allocate the required memory in
the CICS subsystem.
Action: Check your CICS region log to find the causes.
|
045
|
unable to allocate memory.
Explanation: The RSP issued an OPENPIPE command for
a DB2 output pipe, and the Server Option was unable to allocate
the required memory in the CICS subsystem.
Action: Check your CICS region log to find the causes.
|
046
|
unable to allocate memory.
Explanation: The RSP issued an OPENPIPE command for
a DB2 output pipe, and the Server Option was unable to allocate
the required memory in the CICS subsystem.
Action: Check your CICS region log to find the causes.
|
047
|
TDESCRIB failed.
Explanation: The RSP issued an OPENPIPE command and TDESCRIB failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
048
|
TDSETUDT failed.
Explanation: The RSP issued an OPENPIPE command and TDSETUDT failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible reasons.
|
049
|
unable to allocate memory.
Explanation: The RSP issued an OPENPIPE command for
a STD output pipe, and the Server Option was unable to allocate
the required memory from the CICS subsystem.
Action: Check your CICS region log to find the causes.
|
050
|
TDESCRIB failed.
Explanation: The RSP issued an OPENPIPE command for
a STD output pipe and TDESCRIB failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
051
|
CICS READQ failed.
Explanation: The RSP issued a GETPIPE command and the CICS
READQ failed.
Action: Check your CICS system logs.
|
052
|
CTBDESCRIBE failed.
Explanation: The CSA issued an OPENPIPE command and CTBDESCRIBE failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
053
|
invalid datatype.
Explanation: The CSA issued an OPENPIPE command, and CTBDESCRIBE returned
an invalid datatype.
Action: List valid datatypes to identify the invalid one.
|
054
|
unable to allocate memory.
Explanation: The CSA issued an OPENPIPE command, and
the Server Option was unable to allocate the required memory in
the CICS subsystem.
Action: Check your CICS region log to find the causes.
|
055
|
CTBBIND failed.
Explanation: The CSA issued an OPENPIPE command and CTBBIND failed.
Action: Refer to the appropriate Mainframe Connect Client Option Programmer’s Reference for
possible causes.
|
056
|
TDSNDROW failed.
Explanation: The RSP issued a PUTPIPE command for a
STD pipe and TDSNDROW failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
057
|
TDSNDROW failed.
Explanation: The RSP issued a PUTPIPE command for a
DB2 pipe and TDSNDROW failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
058
|
TDSNDDON(TDS_DONE_CONTINUE) failed.
Explanation: The RSP issued a CLOSPIPE command and TDSNDDON (TDS_DONE_CONTINUE)
failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
059
|
TDSTATUS failed.
Explanation: The RPC issued a command and TDSTATUS failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
060
|
TDCANCEL failed.
Explanation: The RPC issued a command and TDCANCEL failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
061
|
TDNUMPRM failed.
Explanation: The RPC issued an RPSETUP command and TDNUMPRM failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
062
|
TDINFPRM failed.
Explanation: The RPC issued an RPSETUP command and TDINFPRM failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible causes.
|
063
|
invalid parm type, must be character.
Explanation: The RSP was invoked with parameters that are not of type
character.
Action: You invoked the RSP with an invalid parameter. Correct the
syntax error.
|
064
|
unable to allocate memory.
Explanation: The RSP issued an RPSETUP command, and
Open Server is unable to allocate the necessary memory from CICS.
Action: Check your CICS region log to find the causes.
|
065
|
unable to allocate memory.
Explanation: The RSP issued an RPSETUP command, and
Open Server is unable to allocate the necessary memory from CICS.
Action: Check your CICS region log to find the causes.
|
066
|
TDRCVPRM failed.
Explanation: The RPC issued an RPSETUP command and TDRCVPRM failed.
Action: Refer to the appropriate Mainframe Connect Server Option Programmer’s Reference for
possible reasons.
|
072
|
invalid pipe format specified.
Explanation: The RSP attempted to open a pipe but specified an invalid
pipe format.
Action: Review your code and correct it. Valid specifications for
SPFORMAT are STD, DB2, BIN, and MIX.
|
073
|
invalid pipe mode specified.
Explanation: The RSP attempted to open a pipe but specified an invalid
pipe mode.
Action: Review your code and correct it. Valid specifications for
SPMODE are INPUT and OUTPUT.
|
074
|
Valid SQLDA not found.
Explanation: The RSP attempted to open a DB2 format output pipe but was
not supplied a valid SQLDA.
Action: Review your code and correct it. This error can occur if the
field SPSQLDA has not been set or the address in the SPSQLDA does
not point to a valid SQLDA. The SQLDA field SQLDAID must contain
the eye-catcher SQLDA.
|
075
|
Pipe not open for output/input.
Explanation: The RSP or CSA is attempting to read or write to the pipe
but the pipe is not open.
Action: Review your code and correct it.
|
076
|
invalid status issued.
Explanation: The RSP issued a STATUS command but specified
an invalid value for SPSTATUS.
Action: Review your code and correct it. Valid specifications for
SPSTATUS are OK, E, and W.
|
078
|
Pipe already open for output/input.
Explanation: The RSP or CSA attempted to open a pipe but the pipe is already
open.
Action: Review your code and correct it.
|
082
|
sql buffer address not specified.
Explanation: The CSA issued a REQEXEC command but did
not supply the address of a buffer containing the SQL statements.
Action: Review your code and correct it.
|
083
|
no results pending.
Explanation: The CSA issued an OPENPIPE command, but
result data is not available.
Action: No action is required.
|
085
|
ct_connect failed - unable to allocate conversation.
Explanation: The CSA issued an ATTACH command, but
the access module was unable to allocate a session/conversation
to the partner specified by the server (attachment) name.
Action: Check to see if the connection is active in CICS, VTAM, and/or
SNA communications software. Verify that Mainframe Client Connect
is installed and operational. Also, verify that the Open Client
Router/Server table is loaded in the CICS region. Refer
to the Mainframe Connect Client Option for CICS Installation and Administration Guide.
|
