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


Article ID: 50016


Updated On:


CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD




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:



Component: CCIMVS