This document covers the following topics:
(UNIX and Windows)
+---------------------------------------------------------------------+ ! ! ! Modify Event Definition ! ! Linux ! ! Event Type ==> X X Exit Code J Job special event ! ! R Exit A Add. Job-ok, Job-not-ok ! ! S String ! ! ! ! ! ! Exit Code is ==> >_ than ==> 0___ ! ! ! ! Exit ==> ________ in NAT Library ==> ________ Exit Mode ==> _ ! ! ! ! String ==> ______________________________ missing ==> _ ! ! in File ==> ______________________________________________________ ! ! ! ! ! ! Occurrence of event means OK or NOT OK ==> NO ! ! ! ! Enter-PF1---PF2---PF3-----------PF5-------------------------------- ! ! Help Add End Save ! +---------------------------------------------------------------------+ |
| Field | Description | |
|---|---|---|
| Event Type | Type of event to be checked. Possible values: | |
| A | Additional definition for job ok or job not ok. See Example of an A-type Event. | |
| J | Job special event. | |
| R | Job SYSOUT is to be checked by a user exit. See Example of an R-type Event. | |
| S | Occurrence of a specific string in job SYSOUT .
See Example of an S-type Event.
Notes:
|
|
| X | Exit code. | |
| Operator | (for a X-type event) Specify a logical operator to compare the received return code with the value entered in the Event Type field. Possible values: | |
| = or EQ | Exit code is equal to specified value. | |
| >= or GE | Exit code is greater than or equal to specified value. | |
| > > or GT | Exit code is greater than specified value. | |
| <= or LE | Exit code is lower than or equal to specified value. | |
| < or LT | Exit code is lower than specified value. | |
| <> or NE | Exit code is different from specified value. | |
| User Exit |
(for an R-type event) Name of the end-of-job check user exit which is to run on job termination. Entire Operations will perform an Entire System Server logon to the job’s execution node with the job’s submit user ID prior to the execution of the exit. See also the section Editing End-of-Job User Exits. |
|
| in Natural Library | (for an R-type event) The Natural library in which the user exit resides. This library should be different from the Entire Operations system library. | |
| Exit Mode | ' ' (blank) | Exit will be executed synchronously. (Default) |
| 'A' | Exit will be executed asynchronously (in a Natural task). | |
| String | This string will be searched for
in the SYSOUT or any defined file. If the string is found, the event is
satisfied. If the search string 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' The search string may contain symbols. Symbols with activation escape characters will be replaced at job activation time. Symbols with submit escape characters will be replaced at end-of-job checking time. Missing symbols will cause a permanent activation error or permanent end-of-job checking error. |
|
| missing |
String missing: If "Y" is defined here: If the string is not found, the event will be satisfied. |
|
| in File | If a UNIX or Windows file is
specified here, it will be scanned for the search string. Symbol replacement is
possible for the file name or any part of it:
If this field is left blank, the SYSOUT will be scanned. Symbol replacement is possible. The submission escape character is to be used. |
|
| Occurrence of event means OK or NOT OK | Specify the event check status, if defined event occurs. Possible values: | |
| OK | Check ok. | |
| NO | Check not ok. | |
| -- | No effect on the job result. | |
|
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. See Example of an A-type Event. Note: |
||