Using a Stored Event Handler Record in z/OS

In this example, a demand-driven UEM Server will watch for the creation of a file called uemtest.dat. Since no path is specified, it will look for this file in the user's UEM Server working directory, as specified in the component definition for a demand-driven UEM Server.

If the file completes before the inactive time of 17:38 elapses, the event occurrence will be set to the triggered state, and UEM will execute the command or script contained in the event handler h001, which is the ID of a record in the event handler database.

If the file does not complete before the inactive time elapses, the event occurrence will be set to a rejected state. Since no event handler information is provided for a rejected occurrence, no further action will be taken by the UEM Server.

If the UEM Server does not detect the presence of uemtest.dat before the inactive time of 17:38 elapses, the event will be set to an expired state.

SYSIN Options

The SYSIN options used in this example are:

Option	Description
-event_type	Type of event to monitor.
-filespec	Name or pattern of the file whose creation should be detected and tracked for completion.
-wait	Forces the UEM Manager to wait for the completion of the UEM Server.
-inact_date_time	Date and time at which the state of the monitored event should be made inactive.
-triggered	Event state that, when encountered, will result in the execution of the associated event handler.
-handler_id	ID of a stored event handler record.
-host	List of one or more hosts upon which a command may run.
-userid	ID of a remote user account that the UEM Server uses to establish the security context in which event monitoring is performed.
-pwd	Password associated with -userid.
-max_count	Maximum number of event occurrences to monitor.

Components

Universal Event Monitor Manager for z/OS

Universal Event Monitor Server