SYSVIEW for IMS question
Article ID: 120012
Updated On:
Products
SYSVIEW Performance Management
NXBRIDGE - SYSVIEW/ENDEVOR
Issue/Introduction
Is there a way that I can set up an alert in SYSVIEW to flag any transaction in my system that have not executed for the past 30 minutes???
So, starting at midnight, at 12:30, I want an alert issued for all transactions that have not executed since midnight, then at 1 AM I want an alert for all transactions that have not executed since 12:30 etc, etc.
So, starting at midnight, at 12:30, I want an alert issued for all transactions that have not executed since midnight, then at 1 AM I want an alert for all transactions that have not executed since 12:30 etc, etc.
Environment
Release:
Component: SYSVW
Component: SYSVW
Resolution
Although
the functionality does not exist with SYSVIEW itself, what you are asking for would be pretty simple to do if you used OPS/MVS for the scheduling and notification,and let SYSVIEW provide the data to OPS/MVS when the IMS transactions end. Here’s a simplified outline:
·
Create
a TOD rule in OPS/MVS that fires every 30 minutes. On the initial enablement of the rule, it would only create global variables that represented the IMS transactions that are to be monitored. Something with a format like GLVTEMPx.imsid.imstran,
where imsid is the IMS subsystem id, and imstran is the transaction id. For times other that the initial time the rule fires, create
some sort of alert message, or notification for any of the global variables that still existed.
The assumption would being that the global variable would be deleted when the transaction ran. Then after all notifications have been processed, rebuild the list of global variables for the next 30 minute interval.
Create
an API event rule (see the topic ‘CA OPS/MVS Event Notification’ from TOPICS). The sole purpose of the API event rule would be to delete the global variable so that the next time the TOD rule fires, there would not be any alert/notification.
·
Create
a SYSVIEW threshold definition for IMS variable IMTRLIFE. The IMSTRLIFE definition would specify the ID (IMS ID), Resource (transaction name), and set OPSMVS to YES so that the API event would trigger.
The hard part of this would be figuring out a schedule for the TOD rule as you probably don’t want this to be done on holidays, or other days when the IMS transactions don’t run.
the functionality does not exist with SYSVIEW itself, what you are asking for would be pretty simple to do if you used OPS/MVS for the scheduling and notification,and let SYSVIEW provide the data to OPS/MVS when the IMS transactions end. Here’s a simplified outline:
·
Create
a TOD rule in OPS/MVS that fires every 30 minutes. On the initial enablement of the rule, it would only create global variables that represented the IMS transactions that are to be monitored. Something with a format like GLVTEMPx.imsid.imstran,
where imsid is the IMS subsystem id, and imstran is the transaction id. For times other that the initial time the rule fires, create
some sort of alert message, or notification for any of the global variables that still existed.
The assumption would being that the global variable would be deleted when the transaction ran. Then after all notifications have been processed, rebuild the list of global variables for the next 30 minute interval.
Create
an API event rule (see the topic ‘CA OPS/MVS Event Notification’ from TOPICS). The sole purpose of the API event rule would be to delete the global variable so that the next time the TOD rule fires, there would not be any alert/notification.
·
Create
a SYSVIEW threshold definition for IMS variable IMTRLIFE. The IMSTRLIFE definition would specify the ID (IMS ID), Resource (transaction name), and set OPSMVS to YES so that the API event would trigger.
The hard part of this would be figuring out a schedule for the TOD rule as you probably don’t want this to be done on holidays, or other days when the IMS transactions don’t run.
Feedback
Yes
No
Powered by
