Hi Jan,
These messages would suggest possible slow downs when these messages appear in the log at attempts to obtain data. Prior to requesting the data CA SYSVIEW will issue a call to CCI to present a list of eligible systems, and if the system isn't in the list it shouldn't issue the request to the system, so if the system is down you would normally not continue to see the failed CCI calls. In the messages you are receiving it appears increasing the timeout values may help in reducing or eliminating the messages from coming out. So the recommendation is to increasing the following to at least 15 to see if it reduces the messages being generated now.
XscrCancelSessionTimeout 5
XscrGetCommandDataTimeout 5
XscrGetIdentTimeout 5
XscrGetStatusTimeout 5
XscrGetUserTimeout 5
XscrSendOsCommandTimeout 5
XscrStopSessionTimeout 5
XsdsSendTimeout 5
XsmsSendTimeout 5
XSPingTimeoutDefault 5
XssiReceiveInitialTimeout 5
XssiSendEndTimeout 5
XsssSendTimeout 5
XsxiReceiveInitialTimeout 5
XsxiSendEndTimeout 5
XsxsSendTimeout 5
These parameters can be found in the XSYSTEM member of the CA Sysview PARMLIB (CNM4BPRM).
Best regards
Hennie Hermans
------------------------------
Principal Support Engineer
CA Technologies, A Broadcom Company
------------------------------
Original Message:
Sent: 02-13-2020 02:21 AM
From: Jan Rypel
Subject: CCI CONVERSE failed
Hi guys.
I found in Sysview log this messages, do you have any idea, what are they about?
GSVX345E (MVSDATA) #CCI CONVERSE failed, rc 08 vrc 226E0000 xrc 6E000000
GSVX348E (MVSDATA) Client origid CCIBSYS.XSCR.00000228.00000001.00000010.007C116
GSVX347E (MVSDATA) Server destid CCIASYS.XSDS.0980.GSVX.ASYS
GSV2602E (MVSDATA) Communication failed with system ASYS job SYSVUSER server XSD
GSVX346E (MVSDATA) #CCI CONVERSE failed, RECEIVE HAS TIMED OUT
I manual I'v seen only this:
GSVX346E <request> failed, <errtext>
A request to CA Common Services for z/OS has failed.
All cci connections are ok, no errors there.
We are running on Sysview 15 (PTF10)
Thank you