Attempting connection to CICS on wrong TCP/IP port

If CICS® Transaction Gateway attempts to connect to CICS on the wrong TCP/IP port an error occurs.

Symptom

The following error is returned:

ECI_ERR_NO_CICS

Probable cause

The CICS server is listening on a different TCP/IP communications port to the one through which CICS Transaction Gateway is attempting the connection. This is because the SERVER section of the CICS Transaction Gateway configuration file (ctg.ini) is specifying the wrong port number.

Action

Check which port the CICS server is listening on. To check the port an IPIC TCPIPService is defined to listen on in CICS Transaction Server:
On TSO option 6, issue the command:
```
NETSTAT ALLCON (APPLD *CISS*
```
On USS, issue the command:
```
netstat -a -G *CISS*
```
Sample output:
```
IY2GTGA2 0005AD5F Listen
 Local Socket:   1.23.456.789..1120
 Foreign Socket: 2.34.567.890..43066
 Application Data:  DFHIIY2GTGA2CISSIPIC    IP50889
IY2GTGA2 0005DB97 Establsh
 Local Socket:   1.23.456.789..1120
 Foreign Socket: 2.34.567.890..43066
 Application Data:  DFHIIY2GTGA2CISSIPIC    0000000700000007
```
This example shows that the IPIC TCPIPService is listening on port 50889 and also that an IPCONN is in use. The generated IPCONN name is 00000007.
Change the port number in the configuration file (ctg.ini). For more information, see Port.

Additional information

The Application Data string in the example contains these values:

DFH: The CICS Transaction Server prefix.
I: Inbound.
IY2GTGA2: The CICS APPLID.
CISS: The listening transaction CISS for inbound IPIC requests.
IPIC: The TCPIPService.
IP50889: The TCPIPService name.
0000007: The generated IPCONN name.