Event Object (EVNT)

You define Event objects to monitor certain conditions and, if they apply, to automatically trigger actions, usually the execution of further objects, as defined in its Event Process page. They are in Sleeping status as long as their frequency and time parameters do not apply and change to Checkingwhen they do.

There are various types of Event objects:

• CONS (Console) monitor the messages returned by target systems.
• DB (Database) monitor values in tables.
• FILE check file-related conditions, for example if the defined number of files has been transferred via FTP into a directory, or if a file is stable, etc.
• RULE
• TIME

You can use the following functions of the Automic scripting language to retrieve relevant data for the Event object:

• For Console, File and Database Events: GET_CONSOLE, GET_EVENT_INFO
• For File Events: GET_FILESYSTEM
• For Windows Events: GET_WIN_EVENT

Object Definition

Object class: Executable object

Object type/Short name: EVNT

Subcategories: TIME, FILE, DB, CONS, RULE

Defining Event Objects

The steps for defining Event objects (EVNT) are the same as for any other Automic object.

1. Define the settings on the standard pages that are always available for all objects:
   • General Page
   • Version Management Page
   • Documentation Page
2. Define then the necessary parameters on the pages that are specific for all executable objects:
   • Process Pages
   • Attributes Page
   • Variables & Prompts Pages
   • Rollback Page
3. Define the Event specific settings. There are five Event object types, namely:
   • Defining CONS Event Objects
   • Defining DB Event Objects
   • Defining FILE Event Objects
   • Defining TIME Event Objects
   • Defining RULE Event Objects
4. Optionally, enter the script to be processed with the event in the Event Process Page.
5. You can also modify the Event Object Attributes, if necessary.

Next steps:

Define the Actions that the Event will Trigger

You do this on the Event Process Page.

Execute the Event Object

The execution of an Event object usually triggers the execution of other objects; those objects may in turn trigger the execution of further tasks. In the Process Monitoring perspective on the various lists of Executions related to the Event object, the tasks resulting from these executions are displayed as children of the Event and are flagged with a special tag type, namely !EVNT. This way you can easily check which executions were triggered by a specific Event.

See Monitoring Events for details on how the Event Monitor works as well as Execution Data for information on Execution data.

Event objects can be included in Schedule Objects (JSCH) and thus be executed automatically at predefined times and/or intervals. Likewise, they can be part of workflows (see Workflow Overview).

Of course, you can also manually execute, restart or stop them. For details see Executing Event Objects.

If you want to check the number of times the system checked the Event, go to the Check count section on its Details.

Monitor the Event

Immediately after executing the object you can start monitoring it. Right-click it to select Monitoring and open the pre-filtered list of tasks to display this one. See Monitoring.

In the Process Monitoring perspective you can then follow their progress and access the reports and statistical information associated to them.

Active Events can be canceled (they assume then the Abend/manually canceled status), quitted (they end cleanly with Ended_OK status) or suspended (this keeps the Event active but temporarily disabled).

See Working with Tasks, particularly Stopping and Interrupting.

See also: