Jobs Waiting on Events

Jobs can wait for one or more events, this forms the basis of event-driven process scheduling. You specify as many events as you need to be waited on. The jobs based upon those definitions cannot be executed before the events upon which they are dependent are raised. When a job is created for a definition, it inherits all the events to be raised, and must wait for those.

A job waits only once for a specific event. So if the event was raised but the job did not start (for example, due to the closing of a job queue), the job does not wait again for an event from the same event definition the next time the job is released.

When a job waits for an event it gets the EventWait status.

Automatically started jobs

A event-waiting job can be auto-started when the event is raised. Make sure that all job parameters (if any) have default parameter values. You can set auto-start to:

Never - A job will never be submitted.
Always - A job will always be submitted.
Only one - Only submit a job when there is no job of the same job definition in status New, Initial, or Pending.

Note Note

An event-waiting job must first be scheduled before it gets the EventWait status.

End of the note.

Clearing events

The job that is triggered by the event should clear the event, so that another event-waiter (created later) will wait for another occurrence of the event.

The following substitution parameters are available for raiser and clearer comments in job definitions and job chains:

${jobid} - The job id of the raiser job
${jobdescription} - the raiser job name, as displayed by the job monitor at the time of raising the event.
${jobstatus} - The status of the job at the time it raised the event.

Values

Tab	Field	Description	Default Value
Wait Events	Event Definition	The event definition the job will be waiting for.
Wait Events	Auto Submit	Should the job start automatically each time this event is raised?	Never.
Wait Events	Clears Event	Should the start of the job clear the event?	No.
Wait Events	Clear Comment