How to stop CAS9855I and CAS9899W messages?
Article ID: 19545
Updated On:
Products
Issue/Introduction
Getting too many CAS9899W and CAS9855I messages in the SYSLOG being generated by task CCITCPGW (or CCISSLGW). Running multiple LPARs in the SYSPLEX but some LPARs are normally down during the day to conserve CPU resources. Noticing 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.
How can we 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
Resolution
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.
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 Article 50016 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.
Feedback
