GSV2602E | Communication Failed_Intermittent Occurrence
Article ID: 138796
Updated On:
Products
Issue/Introduction
I am receiving the following errors in both Sysview tasks:
SYSVIEW:
GSVX346E (MVSDATA) #CCI CONVERSE failed, RECEIVE HAS TIMED OUT
GSVX345E (MVSDATA) #CCI CONVERSE failed, rc 08 vrc 226E0000 xrc 6E000000
GSVX348E (MVSDATA) Client origid Server1.XSCR.000002A4.00000001.00000010.008B0E88
GSVX347E (MVSDATA) Server destid Server2.XSDS.0980.GSVX.XXXX
GSV2602E (MVSDATA) Communication failed with system XXXX job SYSVUSER server XSD
GSVX346E (MVSDATA) #CCI CONVERSE failed, RECEIVE HAS TIMED OUT
GSVX345E (MVSDATA) #CCI CONVERSE failed, rc 08 vrc 226E0000 xrc 6E000000
GSVX348E (MVSDATA) Client origid Server1.XSCR.000002A4.00000001.00000010.008B0E88
GSVX347E (MVSDATA) Server destid Sever2.XSDS.0980.GSVX.YYYY
GSV2602E (MVSDATA) Communication failed with system YYYY job SYSVUSER server XSD
SYSVUSER:
GSVX346E (XSDS) #CCI SEND failed, RECEIVER NOT FOUND
GSVX345E (XSDS) #CCI SEND failed, rc 08 vrc 06110000 xrc 11000000
GSVX347E (XSDS) Server origid Server1.XSDS.0980.GSVX.XXXX
GSVX348E (XSDS) Client destid Server2.XSCR.000002DC.00000001.00000009.008C6B48
GSVX346E (XSSS) #CCI SEND failed, RECEIVER NOT FOUND
GSVX345E (XSSS) #CCI SEND failed, rc 08 vrc 06110000 xrc 11000000
GSVX347E (XSSS) Server origid Server1.XSSS.0980.GSVX.XXXX
GSVX348E (XSSS) Client destid Server2.XSCR.000002DC.00000001.00000009.008C6B48
GSVX346E (XSDS) #CCI SEND failed, CCI LINK HAS SHUTDOWN/IS SHUTTING DOWN
GSVX345E (XSDS) #CCI SEND failed, rc 08 vrc 0ADF0000 xrc DF000000
GSVX347E (XSDS) Server origid Server1.XSDS.0980.GSVX.XXXX
GSVX348E (XSDS) Client destid Server2.XSCR.000000E0.00000004.00000010.008B1E88
GSVX346E (XSDS) #CCI SEND failed, CCI LINK HAS SHUTDOWN/IS SHUTTING DOWN
GSVX345E (XSDS) #CCI SEND failed, rc 08 vrc 0ADF0000 xrc DF000000
GSVX347E (XSDS) Server origid Server1.XSDS.0980.GSVX.XXXX
GSVX348E (XSDS) Client destid Server2.XSCR.000000E0.00000004.00000010.008B1E88
NOTE: XXXX and YYYY are masked SSID's.
Environment
Release : 17.0; 16.0; 15.0
Component : SYSVIEW
Cause
The GSV2602 is the message to focus on; it identifies a timeout condition that could be influencing the other events. Prior to taking additional action, review and potentially adjust the values noted below, located in the "XSYSTEM" member of CMN4BPRM.
Resolution
Understanding the Message Condition
It's likely the timeouts are the result of higher-priority system requests preventing the receiver from getting CPU-time and not that of a legitimate failure - a symptom of this being the GSV2602 message is only issued occasionally during elevated system work periods.
With this issue, the objective is to increase the values only to where the false alerts cease; setting them to the maximum of '5 minutes' can have detrimental impacts during a legitimate issue as notification would be delayed, needlessly prolonging the problem timeframe.
Incrementing the Values
Assuming the additional resource consumption is valid, users can alter the timeout values associated with the XSYSTEM command:
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
There are four additional related parameters shown below. It's advised to leave them at the default settings unless advised by Sysview Product Support:
XscrConnectTimeout 15
XscrProcessCommandTimeout 180
XssiReceiveInputTimeout 1800
XsxiReceiveInputTimeout 1800
Implementing the Change
This change can be implemented via a COLD start of the SYSVIEW and SYSVUSR address spaces.Or if you don't want to recycle SYSVIEW then you can go to the LIBCACHE screen locate the XSYSTEM member and use RELoad subcmd in front of that XSYSTEM entry to reload new changes.
Additional Information
- It's recommended to increase the values in intervals of '5' but not a steadfast rule; users typically opt to start testing with a value of '15' and work towards the proper value
- Documentation | XSYSTEM Parmlib member
Feedback
