Appendix B
Communication Failure Codes
This appendix describes the codes that are output if there is a communication failure. The communication error may occur during the execute method of the function object.
The CONNECTION structure in the properties data block contains communication status information in the following fields.
A zero value in each of these fields indicates a successful communication process. If the communication process failed, one, or more, of the above fields contain a failure code that can be used to identify the source of the problem.
CONNECTION.RC
Table B-1 lists the most common causes for CONNECTION.RC errors.
Table B-1 CONNECTION.RC Errors
|
Error Code
|
Description and Action
|
|
05
|
Session not bound, allocation failed
Description: Conversation can not be started because the session is not bound. This could be a configuration or operational problem.
Action: If this connection has worked before, contact the network operator in order to activate the connection.
|
|
20
|
Transaction id error
Description: The transaction id does not exist (mainframe only).
Action: Check the application table to check whether the application exists or whether a default entry is present
|
|
43
|
Error on getting application record
Description: A conversation state error has been encountered. The application has issued a request incompatible with the current state. This is probably due to a programming error.
Action: Check the protocol according to protocol specifications.
|
|
81
|
Async: connection record not yet arrived
Description: A connection record has been passed to the non-blocking interface but the result is not yet available. This happens when the non-blocking application tries to check whether a reply is available. This is not necessarily an error and should be handled by the application. The conversation continues.
Action: The calling program must retry later with the same connection record.
|
|
82
|
Async: Timeout
Description: A timeout occurs when communicating through the non-blocking interface. This is similar to error type 81.
Action: The calling program must retry later with the same connection record.
|
|
83
|
Timeout - cleanup
Description: A call to SRVRQT has timed out. The problem is probably caused by the remote application which is not responding. The session is cleaned up and the sockets are closed.
Action: Correct the remote application or supply a larger timeout value.
|
|
91
|
Application Table Missing or Invalid
Description: The application table is missing in the path specified by the SRVAPPL specification and in the working directory.
Action: Specify the SRVAPPL environment variable to point to a valid application table or create a valid application table in your working directory.
|
|
92
|
Workstation communication error
Description: the connection is lost during the conversation. The most probable cause for this is that the remote application has abended. If this is not the case, the session was deactivated by force.
Action: Find the cause of the remote application abend and correct the problem. If the remote application was not abended check whether the connection was force deactivated.
|
CONNECTION.RelayRC
These are the same as those listed for CONNECTION.RC. in Table B-1.
CONNECTION.StubRC
The possible values for CONNECTION.StubReason are listed in Table B-2.
Table B-2 CONNECTION.StubReason codes
|
StubReason
|
Code
|
|
CICO_XL_SUCCESS
|
DC C'00'
|
|
CICO_XL_LINKERR
|
DC C'01'
|
|
CICO_XL_NOTPREPARED
|
DC C'02'
|
|
CICO_XL_ALREADYPREPARED
|
DC C'03'
|
|
CICO_XL_MUSTROLLBACK
|
DC C'04'
|
|
CICO_XL_COMMITFAILED
|
DC C'05'
|
|
CICO_XL_ROLLBACKFAILED
|
DC C'06'
|
|
CICO_XL_SIGNONFAILED
|
DC C'07'
|
CONNECTION.StubReason
Possible values for the CONNUNICATION.StubReason can be found in the CICS documentation.