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

This document covers the following topics:


Example of an A-type Event

(z/OS)

  24.10.08               ***** Entire Operations *****                    13:17:08
  Owner   SN            End-of-Job Checking + Actions   MVS/ESA   Job JOB1
  Network  +--------------------------------------------------------------+
  -------- !                                                              ! ----
  C Action !                   Add Event Definition                       !   OA
  _        !  Event Type ==> a  C  Termination Code            MVS/ESA    !
  _        !  +---------------------------------------------------------+ !
  _        !  !                                                         ! !
  _        !  !    Event Definition: Additional 'Job ok/not ok'         ! !
  _        !  !                                                         ! !
  _        !  !  This screen can be used to define an additional        ! !
  _        !  !  Job-ok or Job-not-ok event, to define multiple         ! !
  _        !  !  End-of-Job actions.                                    ! !
  ******** !  !                                                         ! ! ****
  _  C     !  !  The event is for OK or NOT OK ==> __                   ! !
  _        !  !                                                         ! !
  -------- !  ! Enter-PF1------PF3-------PF5---------------------       ! ! ----
  A Activa !  !       Help     End       Save                           ! ! ther
  P Descr. !  +---------------------------------------------------------+ !  Rtn
           ! Enter-PF1---PF2---PF3-----PF5-----------------------------   !
  Command  !       Help  Add   End     Save                               !
 Enter-PF1 +--------------------------------------------------------------+ 2---
       Help  Add   End         Save        Up    Down                    Menu

Explanation:

This screen can be used to define an additional Job ok or Job not ok event, to execute multiple End-of-Job actions of the same type.

Usually actions are defined at the job level with the events All checks ok or Any check not ok. If you want to define an action of the same type two or more times for one of these events, you need additional event entries for Job ok or Job not ok.

Note:
You can use these additional event definitions to set conditions, but it is not recommended, because they are not evaluated for the display of job dependencies (see Displaying Job Dependencies in the section Job Maintenance).

Example of a C-type Event

(z/OS)

  24.10.08               ***** Entire Operations *****                    13:35:00
  Owner   SN            End-of-Job Checking + Actions   MVS/ESA   Job JOB4
  Network  +--------------------------------------------------------------+
  -------- !                                                              ! ----
  C Action !                   Add Event Definition                       !   OA
  _        !  Event Type ==> C  C  Termination Code            MVS/ESA    !
  _        !                    R  User Exit                              !
  _        !                    S  String       A  Add. Job-ok,-not-ok    !
  _        !                                                              !
  _        !  Stepname ==> ANYSTEP_______________________                 !
  _        !  Operator ==> EQ   Event ==> C0003                           !
  _        !                                                              !
  _        !  User Exit ==> ___________ in NATURAL Library ==> ______     !
  ******** !                                                              ! ****
  _        !  String ==> ____________________________________________     !
  _        !  Select ==> ________ ________ ________ ________ ________     !
  -------- !             ________ ________ ________ ________ ________     ! ----
  A Activa !  Occurrence of event means OK or NOT OK ==> NO               ! ther
  P Descr. !                                                              !  Rtn
           ! Enter-PF1---PF2---PF3-----PF5-----------------------PF12--   !
  Command  !       Help  Add   End     Save                      Menu     !
 Enter-PF1 +--------------------------------------------------------------+ 2---
       Help  Add   End         Save        Up    Down                    Menu

Explanation:

If return code C0003 is received at any step during job execution, the event result will be not ok.

Example of an R-type Event

(z/OS)

  24.10.08               ***** Entire Operations *****                    13:40:07
  Owner   SN            End-of-Job Checking + Actions   MVS/ESA   Job JOB4
  Network  +--------------------------------------------------------------+
  -------- !                                                              ! ----
  C Action !                   Add Event Definition                       !   OA
  _        !  Event Type ==> R  C  Termination Code            MVS/ESA    !
  _        !                    R  user exit                              !
  _        !                    S  String       A  Add. Job-ok,-not-ok    !
  _        !                                                              !
  _        !  Stepname ==> ______________________________                 !
  _        !  Operator ==> __   Event ==> _____                           !
  _        !                                                              !
  _        !  User Exit ==> UR1________ in NATURAL Library ==> USER__     !
  ******** !                                                              ! ****
  _        !  String ==> ____________________________________________     !
  _        !  Select ==> ________ ________ ________ ________ ________     !
  -------- !             ________ ________ ________ ________ ________     ! ----
  A Activa !  Occurrence of event means OK or NOT OK ==> NO               ! ther
  P Descr. !                                                              !  Rtn
           ! Enter-PF1---PF2---PF3-----PF5-----------------------PF12--   !
  Command  !       Help  Add   End     Save                      Menu     !
 Enter-PF1 +--------------------------------------------------------------+ 2---
       Help  Add   End         Save        Up    Down                    Menu

Explanation:

User exit UR1 checks the job SYSOUT at job completion. This exit resides in Natural library SYSEORU.

Start of instruction set To edit the user exit

Example of an S-type Event

(z/OS)

  24.10.08               ***** Entire Operations *****                    13:44:16
  Owner   SN            End-of-Job Checking + Actions   MVS/ESA   Job JOB4
  Network  +--------------------------------------------------------------+
  -------- !                                                              ! ----
  C Action !                   Add Event Definition                       !   OA
  _        !  Event Type ==> S  C  Termination Code            MVS/ESA    !
  _        !                    R  User Exit                              !
  _        !                    S  String       A  Add. Job-ok,-not-ok    !
  _        !                                                              !
  _        !  Stepname ==> ______________________________                 !
  _        !  Operator ==> __   Event ==> _____                           !
  _        !                                                              !
  _        !  User Exit ==> ___________ in NATURAL Library ==> ________   !
  ******** !                                                              ! ****
  _        !  String ==> EXCEEDS_______________________                   !
  _        !  Select ==> SM*_____ ________ ________ ________ ________     !
  -------- !             ________ ________ ________ ________ ________     ! ----
  A Activa !  Occurrence of event means OK or NOT OK ==> NO               ! ther
  P Descr. !                                                              !  Rtn
           ! Enter-PF1---PF2---PF3-----PF5-----------------------PF12--   !
  Command  !       Help  Add   End     Save                      Menu     !
 Enter-PF1 +--------------------------------------------------------------+ 2---
       Help  Add   End         Save        Up    Down                    Menu

Explanation:

If the string EXCEEDS appears in any system message, the event result is not ok.

If you enter NE or <> in the Operator field, the event occurs if the string is not found.

If the string to be searched for contains at least one blank at the beginning, in the middle or at the end, it must be enclosed in single quotes. For example:

'    leading blanks'

Notes:

  1. All checks of the SYSOUT file and actions which refer to the SYSOUT file, are not executed, if no SYSOUT file is available. This case only applies, if the job is submitted as a temporary dummy job.
  2. A string search in a non-existent file is handled like string not found in an existing file.