When attempting to connect to Server Application (eg: CA-Datacom Server) I get error CCICONV FAILURE: CCI0053 TCP/IP error WSAECONNABORTED

Document ID : KB000055198
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Cannot connect to Server Application (eg: CA-Datacom Server) from a workstation. CCI/pc to CCITCP.

Solution:

First, ensure that the connection is being made to CCITCP (not CCITCPGW). They are two unique protocols for specific types of connectivity. The former, for client-to-host, and what we'll discuss further. The latter for peer-to-peer.

If a client-to-host connection is incorrectly attempted to CCITCPGW you will generally see:

CCI0053 TCP/IP error WSAECONNREFUSED.

The WSACONNABORTED message is indicating that the CCI connection between the desktop/server/pc and the mainframe has been severed somewhere in the network.

Is the "Disable Appl Timeout Value" checked or un-checked in the CCI-PC configurator? Some earlier versions of CCI-PC may have this check-box labeled as "Disable CCI Timeout Value".

If the box is not checked, try checking the box and retry the action that caused the failure. Be certain to apply the changes before the retry is attempted.

When the box is checked off this means you are using CCI's timeout values.

If your CCI-PC configurator does not have this "Disable Appl Timeout Value" check box, you will need to get the latest version installed. The latest versions of CCIPC are 1.1.6B or 2.1

They are available for download from our ftp site here:

ftp://ftp.ca.com/pub/ca90s/

filename: ccipcw32.zip

or

filename: ccipcssl.zip

note: ccipcssl.zip will work with both ssl and non-ssl connections.

We've also seen similar symptoms when the internal CCI PING task terminates the session because it did not received back a valid response from its PINGs . This internal PING task tasks place on the mainframe within CCITCP.

In this situation turning off the CCIPING function may do the trick. You can do this on the fly with modify command:

F CCITCP, PING ,0

As a test, enter the above command and see if this is re-creatable.

If this seems to address the problem, permanently disable the PING process by updating your CCITCP proc with a
//SYSIN DD statement that points to a RECFM=FB LRECL=80 file that contains the line:

PING 0

note: this should start in column 1.

Lastly, we've seen this encountered with PC's that have firewall software that will not allow the PING request through. So, first verify the CCI PING is turned off correctly, then look into any firewall software rules that may be in place.

If none of the above resolves your connection problem, please turn on CCI traces and send them into CA Common Services technical support for review. Following are the required traces and procedures:

Enable the CCI/pc trace from within the configurator "TRACE" Tab.

Enable the mainframe CCITCP trace by entering the following command from THE CONSOLE:

F CCITCP,T,SYSPRINT *TO ACTIVATE TRACE

F CCITCP,NOTRACE *TO DEACTIVATE TRACE

* MAKE SURE SYSPRINT DD SPECIFIED IN CCITCP PROC....

Additional tip for avoiding this is to recommend that the mainframe CCITCP task run at higher priority than the server application.