CCITCPGW receiving CAS9899W since upgrading to CA COMMON SERVICES v14.0

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



CCITCPGW keeps getting these messages every 10 minutes:

CAS9855I Task 1 connecting to peer MY.REMOTE.HOSTNAME(
CAS9899W Task 1 - CCISYSID MY.REMOTE.HOSTNAME not available...waiting

The thing to understand in this example is that the remote connection is trying to connect to port #1721. The connection is being driven as a result of a NODE and CONNECT statement being defined. If CCITCPGW on the remote system is not running with port #1721 defined as its listen port, no connection can be established and the CAS9899W message will be generated as seen here.


STARTING with CCS390 v14.0 CAW0PROC(CCITCPGW) and CAW0PROC(CCISSLGW) execute PGM=CAS9PDPM and use default port #1721.

The previous versions of CCITCPGW (EXEC PGM=CAS9ATPS) used a default port of 7000.
The previous version of CCISSLGW (EXEC PGM=CAS9PDPM) used a default port of 1721.

If you want to have CCITCPGW use a different port #, you need to specify it on the PROTOCOL statement e.g.

where #### is the PORT number. The port being used will display when CCITCPGW starts e.g.

CAS9850I: CCI TCP/IP Server Ready. Port = 1721 Addr = 111.222.333.44

Any subsequent NODE statements defined to drive connections to a remote machine will by default use this same port# obtained from the PROTOCOL statement. If the CCITCPGW task on the remote machine is running with a different port number, then the NODE statement must define the correct port# of the remote machine. For example: