1

UPDATE TYPE

Single character indicating the type of event that triggered the alert:

• I-A new alert was issued.
• U- An existing alert was updated

2

ALERT ID

Numeric value used as a key (index) to identify the alert.

3

CONTROLM

Name of the data center to which the job belongs.

4

MEMNAME

File Name of the job (previously known as Mem Name)

5

ORDERID

Order ID of the job.

6

SEVERITY

Severity of the alert:

• V — Very urgent
• U — Urgent
• R — Regular

7

STATUS

Values:

• Not noticed
• Noticed
• Handled

8

TIME

Time and date that the alert was issued.

Format: yyyymmddhhmmss

9

USER

Name of the user who last modified the status or text of the alert

10

UPDATE TIME

Time and date that the alert was last modified by the user

11

MESSAGE

Full text of the alert

12

OWNER

The Run As user set as owner of the job

13

GROUP

Sub Application of the job (previously known as group)

14

APPLICATION

Application of the job

15

JOB NAME

Name of the job

16

NODE ID

Node or host where the job is run

17

TYPE

Alert type. Valid values:

• R - Regular (Can also be empty). Default.
• B - BIM

18

CLOSED FROM EM

Initial value is empty. If the a Remedy ticket was closed from Control-M/EM, the value is Y.

19

TICKET NUMBER

Remedy ticket number

20

RUN COUNTER

When a job is executed more than once within a scheduling day, this counter uniquely identifies each execution of that job.

This way you know exactly in what instance of the job’s execution the remedy ticket was opened.

21

NOTES

Displays the text that can be edited and saved in Control-M/EM Alerts window.

Enable SendAlertNotesSnmp parameter (set to 1).