How to stop CAS9855I and CAS9899W messages?

book

Article ID: 19545

calendar_today

Updated On:

Products

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 - DB CA Datacom CA Datacom - AD CA Datacom - Server 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

Issue/Introduction

Description:

You are getting too many CAS9899W and CAS9855I messages in the SYSLOG being generated by task CCITCPGW (or CCISSLGW). You run multiple LPARs in your SYSPLEX but some LPARs are normally down during the day to conserve CPU resources. You notice that with some LPARs down "tons" of CAS9899W and CAS9855I messages are generated on the active LPARs from task CCITCPGW. These messages are generated every few minutes.

What can you do to eliminate these messages when the some LPARs are purposefully shutdown?

Example Messages:

06.26.23 STC23762 CAS9855I TASK 3 CONNECTING TO PEER (1.2.3.23):7000
06.26.51 STC23762 CAS9855I TASK 4 CONNECTING TO PEER (1.2.3.35):7000
06.29.28 STC23762 CAS9899W TASK 3 - CACCISB2 (1.2.3.23):7000 NOT AVAILABLE...WAITING
06.29.56 STC23762 CAS9899W TASK 4 - CACCISC3 (1.2.3.35):7000 NOT AVAILABLE...WAITING
06.30.28 STC23762 CAS9855I TASK 3 CONNECTING TO PEER (1.2.3.23):7000
06.30.56 STC23762 CAS9855I TASK 4 CONNECTING TO PEER (1.2.3.35):7000
06.33.33 STC23762 CAS9899W TASK 3 - CACCISB2 (1.2.3.23):7000 NOT AVAILABLE...WAITING
06.34.01 STC23762 CAS9899W TASK 4 - CACCISC3 (1.2.3.35):7000 NOT AVAILABLE...WAITING
06.34.33 STC23762 CAS9855I TASK 3 CONNECTING TO PEER (1.2.3.23):7000
06.35.01 STC23762 CAS9855I TASK 4 CONNECTING TO PEER (1.2.3.35):7000

Explanation:
In the above example you can see two separate task #'s associated with each outgoing connection attempt. In each set of CAS9855I messages the IP address of the remote "target" system is shown along with the port#. The subsequent and corresponding CAS9899W messages shows the CCI SYSID, IP address, and port# of the remote "target" system along with the text stating that the system is not available. Based on the retry value defined on the CCI NODE statement, connections will be reattempted until the system is available or until manually aborted. Based on the above example the retry time is 4 minutes.

Soluton:

To stop the messages now issue the following command:

 F CCITCPGW,DISCONNECT,xxxxxxxx
 

where xxxxxxx is the CCI SYSID of the system that is not available. This name is displayed on the CAS9899W message being generated. Based on the example provided, the following commands will stop the messages from being generated for systems CACCISB2 and CACCISB3...

 F CCITCPGW,DISCONNECT,CACCISB2
 F CCITCPGW,DISCONNECT,CACCISB3

See Technical Document TEC563344 for similar messages that can be generated in a situation where the remote "target" system is available but the port# assigned to the CCITCPGW task is not what is expected.

Environment

Release: CA90SV00200-14-Common Services-for z/OS
Component: