ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

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

book

Article ID: 50016

calendar_today

Updated On:

Products

CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options Compress Data Compression for MVS Compress Data Compression for Fujitsu Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ecoMeter Server Component FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA On Demand Portal CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Datacom/AD

Issue/Introduction

Description:

IPLED in CA COMMON SERVICES v14.0.

CCITCPGW keeps getting these messages every 10 minutes:

CAS9855I Task 1 connecting to peer MY.REMOTE.HOSTNAME(111.22.123.44):1721
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.

Solution:

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.

PROTOCOL(TCPIPGW,####)
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:

NODE(TCPIPGW,remote_hostname:port#,retry,remote_cci_sysid)

Environment

Release:
Component: CCIMVS