ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

IDB2 API Event not triggered when threshold was met

book

Article ID: 186591

calendar_today

Updated On:

Products

SYSVIEW Performance Management Option for DB2 for z/OS Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - SQL Performance Suite Insight Performance Monitor for DB2 UDB for z/OS

Issue/Introduction

The following alert was coded to produce an API event so opsmvs can trap it and produce the alert but it's not working. What's wrong?

CRIT 06:02:44-CURRENT  DB2G remote threads queued: 13283 02/23/20   


 

Environment

Release : 20.0

Component : CA Insight Database Performance Monitor for DB for z/OS

Resolution

To resolve this problem, add MULTIPLE-EXCP-NOTIFY sysparm to the data collector  as shown below:

MULTIPLE-EXCP-NOTIFY=('OPS','SMTP','SNMP')

The QDSTQDBT is a cumulative field and the above sysparm will trigger actions whenever there is any change to that field. 

Additional Information

1. By default, the CA OPS/MVS® Event Management and Automation event, SMTP, and SNMP exception actions are performed only once per active exception (when applicable).
The above parameter allows the actions to be executed again when the exception severity changes or when the exception is detected again (IQL exceptions).

2. Resetting exception time implies that action indicators are reset for that exception and any action will be performed again at specified time.