GSV1050E (0100029D) z/OS Connect Java classes for SYSVIEW loading failed max retries

Products

• SYSVIEW Performance Management

Issue/Introduction

During the start of z/OS Connect the SYSVIEW JVM Data Collector Agent is failing with 

07.46.35 STC00556  +GSV1001I (0100029D) SYSVIEW for JVM Data Collector Agent Release 17.0 Build 1010 started    
07.46.35 STC00556  +GSV1002I (0100029D) Copyright (c) 2025 Broadcom Inc. and/or its subsidiaries.               
07.46.35 STC00556  +GSV1040I (0100029D) Option keyword ssid value GSVX                                          
07.46.35 STC00556  +GSV1040I (0100029D) Option keyword monzcn value ENABLE                                      
07.46.35 STC00556  +GSV1040I (0100029D) Option keyword monzcnreq value ENABLE                                   
07.46.35 STC00556  +GSV1003I (0100029D) Application GSV_BBGZSRVT_0100029D                                       
07.46.35 STC00556  +GSV1042I (0100029D) Target SYSVIEW SSID GSVX Build 1010                                     
07.46.35 STC00556  +GSV1004I (0100029D) Thread eXternalDataInterface ThreadId 17F333000000000D started          
07.46.35 STC00556  +GSV1004I (0100029D) Thread DataCollector ThreadId 17F334000000000E started                  
07.46.40 STC00556  +GSV1050I (0100029D) z/OS Connect Java classes for SYSVIEW loading started                   
07.47.46 STC00556  +CWWKE0001I: The server zosconnect has been launched.                                        
07.48.42 STC00556  +GSV1050E (0100029D) z/OS Connect Java classes for SYSVIEW loading failed max retries        
08.01.42 STC00556  +CWWKF0011I: The zosconnect server is ready to run a smarter planet.  930                    
   930              The zosconnect server started in 848.364 seconds.                                           

Environment

Sysview JVM datacollector

Cause

The agent for z/OS Connect has a default max limit on attempting to install the SYSVIEW interceptors set at 2 minutes.

On systems that are busy, it appears that it might take longer than that. In a joblog where the agent successfully installed the interceptors, it can take around 1 minute.

In the joblog where the agent failed to install the interceptors, the message came out just around the 2 minute mark from when the agent started to try to install.

Resolution

There is an undocumented agent option that can control this limit value.

Like the other options that the agent accepts, options can be specified as parameters at the agent startup or as environment variables.

The following controls how often the agent will attempt to install the interceptors in seconds (default: 2):

     Agent parameter:  monzreqintvl

     Env var:  GsvoMonitorZReqInstallInterval

The following controls the max number of tries the agent will attempt to install the interceptors (default 60):

     Agent parameter: monzreqretry

     Env var: GsvoMonitorZReqInstallRetries

The monzreqretry/GsvoMonitorZReqInstallRetries option should be used. Try setting it to 150.

This means the agent will try a max number of 150 times to install the agent every 2 seconds. 150 * 2 = 300 seconds or 5 minutes.

If the agent still fails to install after 5 minutes, this option can be set even higher. 

Those options should code in the same place where is coded the monzcn and monzcnreq options.

The only thing that needs to be recycled after the option is coded is the z/OS Connect server where the agent is running.Here is an example of these options: 

JVM_OPTIONS=-agentpath:/usr/lpp/isv/cai/sysview/cnm4g00/runtime/jvmdata/bin/libgsvoagt4.so=ssid=GSVX,monzcn=enable,monzcnreq=enable,monzreqretry=150