TCP/IP communication problems

The following are solutions to problems that can occur when communicating over TCP/IP:

A Client daemon running on Windows® cannot load the TCP/IP protocol
driver

You have probably received message CCL3229E in a pop-up window and message CCL3247 in the cicscli.log error log file. These messages indicate you have probably specified the wrong device driver in the configuration file. For all TCP/IP communication, the Client daemon on Windows should use the CCLWNTIP driver. Any vendor offering a WINSOCK interface can use this TCP/IP driver.

Message CCL4404 TCP/IP (to 'CICSTCP') unable to resolve name: RC=2

The CICS® server, in this example CICSTCP, could not be resolved by the TCP/IP protocol driver. Ensure that your domain name server and router address information is correct, and that any names and IP addresses in the TCP/IP etc\hosts file are correct.

Use the TCP/IP ping or nslookup commands to see if TCP/IP can resolve the hostname.

CCIN not recognized, CTIN not recognized

The CCIN transaction installs your Client daemon definition on the CICS server. The CTIN transaction installs your client terminal definition on the CICS server. These transactions must be available on the CICS server if it supports the EPI, because the EPI implies CICS 3270 terminal emulation and CICS 3270 printer emulation. For information on which CICS servers support EPI and hence CICS 3270 emulation, see Table 1. You can ignore these messages if your CICS server does not support the EPI.

A cicsterm command for a mainframe CICS server failed

cicsterm and cicsprnt use CICS 3270 emulation. Some mainframe CICS servers do not support CICS 3270 emulation. For information on which CICS servers support CICS 3270 emulation, see Table 1.