MQS/IMS/JVM timers set with features disabled
search cancel

MQS/IMS/JVM timers set with features disabled

book

Article ID: 259762

calendar_today

Updated On:

Products

SYSVIEW Performance Management

Issue/Introduction

Upgrading from SYSVIEW 15.0 to 17.0 and notice that MQS/IMS/JVM timers are set even though features are disabled. 

GSVX745I (MAIN) GSVXMVS5 |Option-IMS                  No 
GSVX745I (MAIN) GSVXMVS5 |Option-MVS                   Yes
GSVX745I (MAIN) GSVXMVS5 |Option-TCPIP               Yes
GSVX745I (MAIN) GSVXMVS5 |Option-MQ                    No 
GSVX745I (MAIN) GSVXMVS5 |Component-CTG                No 
GSVX745I (MAIN) GSVXMVS5 |Component-DB2                Yes
GSVX745I (MAIN) GSVXMVS5 |Component-Health-Check  Yes
GSVX745I (MAIN) GSVXMVS5 |Component-IDMS               No 
GSVX745I (MAIN) GSVXMVS5 |Component-JVM                No 
GSVX745I (MAIN) GSVXMVS5 |Component-MIM                No

Example of messages at SYSVIEW startup:
GSV2304I (SCHEDULR) Timer event MQS-PAGESETS has been created
GSV2304I (SCHEDULR) Timer event IMS-SYSTEM has been created  

However, using the supplied SCHEDULE parameter member with conditional processing: 

)IF FEATURE=MQ     
   )INCLUDE SCHDMQS
)ENDIF             

Why SCHDMQS is being invoked? 

Environment

SYSVIEW 16.0 & 17.0 - z/OS supported releases - 

Resolution

The changes to the scheduled definitions started with the PTF: 

S015518

and were later revised by the PTF:

LU04404

The changes put in place will now define those scheduled events whether you have the feature turned on or not.

When the scheduled event is defined, it kicks off at a certain interval but if the data collection is not active, it basically does nothing.

It's only when you would start the MQSDATA task that the scheduled events will do anything.