Large volume of GSVC501I messages were created and sent to OPS/MVS within a one minute timeframe

Products

• SYSVIEW Performance Management

Issue/Introduction

During investigation of an OPS/MVS AOF Msg it was discovered that a SYSVIEW rule triggered over 27000 GSVC501I messages within a minute timeframe which led to OPS1372E MLWTO POOL IS FULL error.   

Resolution

OPS/MVS and SYSVIEW both became victims of the issue where the CICS regions had  triggered the SYSVIEW RULE too many times in a short interval, which led to an issue in OPS/MVS where there was a sudden unexpected number of WTOs in a very short time span.   

 

OPS/MVS has a buffer that holds the MLWTOs, and that buffer was exhausted when SYSVIEW was sending too many GSVC501 message that are related to one singular SYSVIEW STATE RULE. 

Using API rules instead should resolve the issue because the API msg that SYSVIEW RULEs are sending will be only one line when WTO is 4 lines.  Content wise they will be equal.

Verify first what OPS/MVS automation is doing.  If it just sending email notifications, then you can do it easily with SYSVIEW  API.  We also recommend reviewing the remainder of the current SYSVIEW RULEs.