End-of-Job Checking and Actions - Overview

This document covers the following topics:

List of End-of-Job Checking and Actions

  • End-of-Job Actions with Execution as a Temporary Dummy Job

  • End-of-Job Checking and Actions Facility

  • Adding Event Definition for z/OS or z/VSE Job

  • Modifying Event Definition for z/OS or z/VSE Job

  • Adding Event Definition for BS2000 Job

  • Modifying Event Definition for BS2000 Job

  • Adding Event Definition for UNIX or Windows Job

  • Modifying Event Definition for UNIX or Windows Job

  • Deleting an Event Definition

  • End-of-Job Checking Defaults for various Operating Systems

  • Creating Online Documentation for Events

  • Adding Output Condition Definitions

  • Modifying Output Condition Definitions

  • Modifying or Setting Master or Active Symbols

  • Displaying Output Condition Use

  • Editing End-of-Job Checking or Action User Exits

  • Defining Activation of Jobs or Job Networks

  • Defining Recovery Action

  • SYSOUT Actions

  • Message Sending

  • Defining End-of-Job Action User Exit

  • Release Resource

See also: Passing Files to Entire Output Management

Defining End-of-Job checking and actions means instructing Entire Operations what actions to trigger after a job has terminated. The triggered action is referred to as an End-of-Job action.

The End-of-Job action depends on the status of the whole job or any other event which can be checked by Entire Operations on termination. The status of the job on termination is determined by the occurrence of certain events during job execution which Entire Operations can check.

Before Entire Operations can check for an event, it must be defined to the system, together with instructions as to the action to be triggered. If no events are specified, Entire Operations performs End-of-Job checking automatically using system defaults.

Events are checked on a check ok/check not ok basis. End-of-Job actions can be triggered by:

  • the result of a single event check (for example: job step level in z/OS);

  • the overall result of the End-of-Job check, which always causes either the event job ok or j ob not ok to occur.

Both of these event definitions are always predefined for every job.

In the latter case, you can define two sets of actions:

  • one set is performed if all checks finished ok (i.e. job ok);

  • the other is performed if at least one check finished not ok (i.e. job not ok).

All actions are performed after the job has terminated.

Kinds of End-of-Job Actions

Possible End-of-Job actions are:

Only one action of the same type can be defined for an event (except in the case of output conditions). If you need several actions of the same type for the event job ok or job not ok, you can define these by adding A type events.

End-of-Job Checks for Various Operating Systems

The following table provides an overview of the availability of various End-of-Job checks for the supported operating systems and environments:

End-of-Job Check z/OS, MSP z/VSE BS2000 UNIX Windows SAP
Termination Codes *   *          
Job Variables     *        
User Exit *   *   *   *   *    
String Search *   *   *   *   *   *  
User Switch     *        
Exit Code       *   *    

An asterisk * indicates that the End-of-Job check is available for the operating system. These checks are described later in this section.