Previous Topic: NotificationsNext Topic: Email Notifications


Monitor States

You can set up notifications to notify users or act when a job reaches a certain state. You can set up notifications for the following job states and conditions:

Abandon submission

Sends a notification when the submission of a job is abandoned.

Note: This state requires that you specify an abandon time for job submission.

Agent down

Sends a notification when the agent referenced in the job definition is down.

Complete

Sends a notification when the job completes successfully.

Exec

Sends a notification when the job starts to execute.

Failed

Sends a notification when the job fails according to its exit code settings.

Force completed

Sends a notification when the job is forced complete.

Global variable wait

Sends a notification if the job is waiting for one or more variable dependencies to be met.

Inactive

Sends a notification if the job is inactive.

Note: This state can only be used with Oracle Applications Single Request jobs.

Monitor

Sends a notification when the condition that the job is monitoring has occurred.

Note: This state can be used with jobs that support continuous monitoring such as File Trigger, Database Monitor, and Database Trigger.

Overdue

Sends a notification when the job is overdue.

Note: This condition requires that you specify an overdue time for job start or completion, or a maximum execution time.

Premature end

Sends a notification when the job ends prematurely.

Note: This condition requires that you specify a minimum execution time.

Ready

Sends a notification when all predecessor dependencies and submit times are met and the job is not held.

Note: The server does not monitor for resource dependencies.

Resource wait

Sends a notification if the job is waiting for one or more resource dependencies to be met.

Step complete

Sends a notification every time a step is completed in a z/OS job. In the notification, you can use the following symbolic variables to identify the steps and completion codes for that execution:

WOB._current_step_name

Specifies the name of the step that was completed.

Example: STEP0012

WOB._current_step_code

Specifies the completion code of the step that was completed.

Examples: S806, 10

Note: If a job is restarted from a particular step, all skipped steps return a completion code of FLUSHED.

Note: This state can only be used with z/OS-Regular and z/OS-Manual jobs.

Suberror

Sends a notification when a submission error occurs, such as when a script is not found.

Unknown

Sends a notification when there is a configuration or system error that the server does not recognize.

Note: Depending on the job type, only a subset of these job states may be available.

More information:

Set Up an Email Notification in the Job Definition

Set Up an Email Notification in the Application

Set Up an Alert Notification in the Application

Set Up an SNMP Notification in the Job Definition

Set Up an SNMP Notification in the Application