Alerting Rule Details

Do not forget to click Save to save Alerting rule definitions.

General

Label

Description of the alert.
Criticality

Alert severity, click on the arrow to select the alert criticality:
- Low : the alert will not be displayed in Job Runs
- Medium or High : the alert will be displayed in Job Runs, in the Actions column
Action Icon

The icon will be displayed in accordance with selected criticality (save for low criticality) and will also be displayed in Job Runs.
Enabled

Check the box to enable this alert setting

Criteria

This section defines the criteria for selection of jobs on which an alert should be sent.

Product

Dollar Universe V6.
Node selection

Click the arrow to select Per node pattern or Per node view and enter the needed information in the corresponding field.
Node pattern

Enter the Node name or the Node pattern (like node*) or click on the arrow to select it from the list.
Node View

Enter the Node View or click on the arrow to select it from the list.
Company

Enter the Company name or click the arrow to select it from the list.
Area

Click the Area(s) targeted by this rule:
- X: Production Area
- S: Simulation Area
- I: Integration Area
- A: Application Area
Monitor

Choose to monitor the execution of a Uproc or a Session:
- Uproc to control the execution of a single job or
- Session to control for the overall implementation of a Session.
In the case of the supervision of the execution of a session, only the fields UG, Session and Task ID can be entered.
Uproc

Enter a Uproc name or use a filter of type A*.
MU

Enter a Management Unit name or use a filter of type A*.
Session

Enter a session or name or use a filter of type A*.
Task ID

Enter a task name or use a filter of type A*.
Submission Account

Enter a submission account name or use a filter of a type A*.
Min. Severity

Set a minimum integer for the Severity parameter. When the Job runs, if its Severity parameter is the same or higher than the Severity specified in the Job Alert Rule, notification can be sent.
Information

Free string (wildcards * allowed). When the Job runs, if its Information parameter matches (with the wildcard values) the information specified in the Job Alert Rule, notification can be sent.
Domain

Enter the name associated to the Uproc or *.
Application

Enter the name of the application associated to the Uproc or name or use a filter of type A*.

Monitor

Alerts can be set on the duration or the status (exclusive choice):

Monitor Duration

Monitors the execution time of the session or Uproc.
- Monitor excessively short execution time: Select this option if an alert should be sent when a Job execution is shorter than the input value. This control is achieved when the Uproc is completed (Completed articles, incidents or Denied). Choose one of the following controls:
  
  Based on statistical runtime: Select this option if an alert should be sent when a Job execution is shorter than x% of the average (obtained from the statistics of performance of this Uproc/MU or Session/MU).
  
  Based on absolute duration: Minimum time in hours, minutes and seconds.
- Monitor excessively long execution time: Select this option if an alert should be sent when the job runs longer than the entered value. Choose one of the following controls:
  
  Based on statistical runtime: Check this option if an alert should be sent when the job runs longer than x% of the average (obtained from the statistics of performance of this Uproc/MU or Session/MU).
  
  Based on absolute duration: Maximum time in hours, minutes and seconds.
- Monitor excessively long Event Wait statuses: Select this option if an alert should be sent when the job waits (Pending and Wait event statuses) longer than the entered value. Choose one of the following controls:
  
  Based on statistical runtime: Check this option if an alert should be sent when the waiting time of a Uproc lasts longer than x% of the average (obtained from the statistics of performance of this Uproc/MU or Session/MU).
  
  Based on absolute duration: Maximum time in hours, minutes and seconds.
  
  A confidence indicator (number of executions) needed to calculate the excessive length can be defined in the Dollar Universe "Dollar Universe – Alert Settings".
  
  No alert is triggered before one minute. Therefore, if the excess duration halfway through indicates a result inferior to one minute, it is set to one minute.
Example: if a Job runs on average in 10 seconds, an alert is sent when the job has exceeded 150% (15 seconds).

But the alert is sent only if the job lasts more than a minute.

The average duration of a Job is displayed in the information associated with the document Job Details. Only completed executions will be used to calculate the average.
Monitor status

Monitors the state of the Uproc or the Session. A Uproc can be monitored during the following statuses:
- Completed
- Aborted
- Launch wait
- Refused
- Time overrun
- Running
- Pending
- Event Wait
- Disabled
For a session, the following statuses can be monitored:
- Running: Session has started but there are still Uprocs to run: not all of the branches have terminated.
- Completed: All branches of the session have ended (Completed or Aborted).

Notification

This section describes the alert sent when an execution matches job and monitoring criteria. Sending a notification is always local to the node in which the alert was detected. Three notification types can be sent:

Dollar Universe SPI for HP Operation Manager
Dollar Universe V6 SNMP supervision
Generic supervision
Email

Notification is optional: If the following boxes are left cleared, an alert will potentially be raised and displayed (depending on the criticity) in the job monitoring without notification being sent.

If the corresponding manager is active on the Dollar Universe node and the monitoring tool is active, an alert can be sent to the manager below (which will forward it to the corresponding module):

Dollar Universe SPI for HP Operation Manager

Additional parameters for HP OM supervision are defined in the Administration mode > Nodes > Nodes > DUAS V6 Node Settings > HP OM Monitoring Node Settings.

Dollar Universe V6 SNMP supervision

Additional parameters for SNMP supervision are defined in the Administration mode > Nodes > Nodes > DUAS V6 Node Settings > SNMP Monitoring Node Settings.

Generic supervision

If none of these Dollar Universe managers is active on the alert's local node, the alert can be transmitted to an external module through the Generic Supervision library. In this case:

On Windows / UNIX / OpenVMS, enter the full path and name of the script to run (special characters not allowed). The script will receive the following arguments (%1, %2 … or $1, $2…or P1, P2…) between inverted commas, corresponding to the run that triggered the alert.
On OS/400, this script must be called u_spv_com.qsh and be located in the node files that generated the alert (data/nodefiles/u_spv_com.qsh).

The script path and name can include variables delimited with ! (for example !S_CODUG!). Usable variables are:

The following variables of the execution context provided by Dollar Universe: S_ESPEXE, S_APPLI, S_CODSESS, S_CODUG, S_PROCEXE, S_SOCIETE, S_CODTSK (as only those variables of the execution context are usable)
Node settings variables
Node variables (Administration > Nodes > Dollar Universe V6 Node > Node Settings > Node Variables)

If the variable is not known, at execution time it is replaced by "" (empty value).

The codes between inverted commas may contain space characters, refer to the " " column in the following tables.

The following arguments are sent by the Generic Supervision to the customer script for all types of alerts:

#arg	Description	Always there	" "	Value
1	Alert Type	Yes	No	JOB_STATUS or SESSION_STATUS or ALERT_TIME_JOB or ALERT_TIME_SESSION
2	Criticalness	Yes	No	LOW / MEDIUM / HIGH
3	Alert label	Yes	Yes
4	Company	Yes	No
5	Area	Yes	No	X / S / I / A
6	Node	Yes	No

Then, the following parameters are not the same, depending on the alert type (specified in arg #1)

Arguments sent by the Generic Supervision to the customer script for an alert on a Job status:

#arg	Description	Always there	" "	Value
7	Uproc	Yes	Yes
8	Uproc version	Yes	No	VVV
9	MU	Yes	Yes
10	Launch number	Yes	No	nnnnnnn
11	Uproc number	Yes	No	nnnnnnn
12	Queue	Yes	No
13	Priority	Yes	No	PPP
14	Application	Yes	No
15	Domain	Yes	No
16	Submission Account	Yes	Yes
17	Processing Date	Yes	No	YYYYMMDD
18	Status	Yes	No	COMPLETED / ABORTED / LAUNCH_WAIT / REFUSED / TIME_OVERRUN / RUNNING / PENDING / EVENT_WAIT
19	Task	No	Yes	"n/a" if not there
20	Task MU	No	Yes	"n/a" if not there
21	Session	No	Yes	"n/a" if not there
22	Session Version	No	No	"n/a" if not there
23	Session Number	No	No	"n/a" if not there
24	Severity	No	No	"n/a" if not there
25	Information	No	Yes	"n/a" if not there

Arguments sent by the Generic Supervision to the customer script for an alert on a Session status

#arg	Description	Always there	" "	Value
7	Session	Yes	Yes
8	Session Version	Yes	No	VVV
9	MU	Yes	Yes
10	Session Number	Yes	No	nnnnnnn
11	Processing Date	Yes	No	YYYYMMDD
12	Status	Yes	No	RUNNING / COMPLETED
13	Task	No	Yes	"n/a" if not there

Arguments sent by the Generic Supervision to the customer script for an alert on a Job time

#arg	Description	Always there	" "	Value
7	ALERT TYPE	Yes	No	TOO_LONG_RUN / TOO_LONG_WAIT / TOO_SHORT
8	Uproc	Yes	Yes
9	Uproc Version	Yes	No	VVV
10	MU	Yes	Yes
11	Launch Number	Yes	No	nnnnnnn
12	Uproc Number	Yes	No	nnnnnnn
13	Queue	Yes	No
14	Priority	Yes	No	PPP
15	Application	Yes	No
16	Domain	Yes	No
17	Submission Account	Yes	Yes
18	Processing Date	Yes	No	YYYYMMDD
19	Status	Yes	No	COMPLETED / ABORTED / LAUNCH_WAIT / REFUSED / TIME_OVERRUN / RUNNING / PENDING / EVENT_WAIT
20	Time Limit	No	No	"n/a" if not there
21	Percentage Limit	No	No	"n/a" if not there
22	Task	No	Yes	"n/a" if not there
23	Task MU	No	Yes	"n/a" if not there
24	Session	No	Yes	"n/a" if not there
25	Session Version	No	No	"n/a" if not there
26	Session Number	No	No	"n/a" if not there
27	Severity	No	No	"n/a" if not there
28	Information	No	Yes	"n/a" if not there

Arguments sent by the Generic Supervision to the customer script for an alert on a Session time

#arg	Description	Always there	" "	Value
7	Alert Type	Yes	No	TOO_LONG / TOO_SHORT
8	Session	Yes	Yes
9	Session Version	Yes	No	VVV
10	MU	Yes	Yes
11	Session Number	Yes	No	nnnnnnn
12	Processing Date	Yes	No	YYYYMMDD
13	Status	Yes	No	RUNNING / COMPLETED
14	Time Limit	No	No
15	Percentage Limit	No	No
16	Task	No	Yes	"n/a" if not there

Example:

"JOB_STATUS" "MEDIUM" "UNIV60" "X" "vmstmpbp01" "HR PAYROLL HEAER" "000" "HR CENTRAL" "0000213" "0000543" "SYS_BATCH" "100" "HR" "C" "admin pay" "20111214" TIME_OVERRUN" "n/a" "n/a" "HR_PAYROLL" "000" "0000034" "n/a" "Session Header"

Send an email message to the specified recipients

SMTP settings are defined in the Administration mode > Nodes > Nodes > Dollar Universe Node Settings > "Dollar Universe – SMTP".

Recipients

The recipients list should contain the email addresses of the recipients separated by a semicolon.

This field can include variables delimited with ! (for example !S_CODUG!). Usable variables are:
- Node variables (Administration > Nodes > Dollar Universe V6 Node > Node Settings > Node Variables)
- Node settings variables
- The following variables of the execution context provided by Dollar Universe: S_ESPEXE, S_APPLI, S_CODSESS, S_CODUG, S_PROCEXE, S_SOCIETE, S_CODTSK (as only those variables of the execution context are usable).
If the variable is not known, at execution time it is replaced by "" (empty value).

The message sent is formatted by Dollar Universe, it contains the context of the execution that triggered the alert. The content is described in the section "Email Notification Content".