This document covers the following topics:

• Adding an Event Definition

• Field Descriptions

• Exit Code Check Error Handling

See also UNIX and Windows Defaults for Event Checking.

---

Adding an Event Definition

To add an event to be checked at job termination

1. Press PF2 (Add) in the End-of-Job Checking and Actions screen.

2. A window opens in which you can enter the event definition:

   12.02.10 ***** Entire Operations ***** 13:18:22 Ow +---------------------------------------------------------------------+ Ne ! ! -- ! Add Event Definition ! --- C ! Linux ! OA _ ! Event Type ==> _ 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 ==> ______________________________________________________ ! -- ! ! --- A ! ! her P ! Occurrence of event means OK or NOT OK ==> __ ! Set ! ! Co ! Enter-PF1---PF2---PF3-----------PF5-------------------------------- ! Ent ! Help Add End Save ! --- +---------------------------------------------------------------------+

Field Descriptions

Meaning of the input fields:

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	Special event during job execution. See Example of a J-type 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. Note: A string search in a non-existent file is handled like string not found in an existing file.
	X	Exit Code Check. This function allows you to check the exit code of a UNIX or Windows job. The result of the event comes from the exit code of a script under UNIX or Windows or from the exit code of a program executable under Windows. Note: A standard check for the exit code can be defined in the Entire Operations defaults. See also Exit Code Check Error Handling.
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) 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	(for an S-type event) Specify the actual string in the job SYSOUT for which Entire Operations is to check. 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.
(String) missing	(for an S-type event) If you enter "Y" here, the event occurs if the string is not found.
in File	(for an S-type event) If you leave this field blank, Entire Operations searches for the String in the SYSOUT collection file created by the Entire Operations Monitor. You can enter another file here to be searched instead. If the file name contains the activation escape character, a symbol replacement is performed (from the active symbol table). The updated file name is stored in the active database.
Occurrence of event means OK or NOT OK	Specify event check status if the defined event occurs. Possible values:
	OK	Check ok.
	NO	Check not ok.
	--	No effect on the job result.

When you are finished defining the event, you can proceed in one of the following ways:

• If you defined an R-type event, you can enter E in the line command field of the event on the End-of-Job Checking and Actions Screen and press Enter to define the user exit using the Entire Operations Editor. (See the subsection Editing End-of-Job User Exits.)

• Press PF2 (Add) to save the definition and clear the window to add another event. You can define any number of events for any one job.

• Press PF5 (Save) to save the event definition(s).

• Press PF3 (End) to close the window and return to the End-of-Job Checking and Actions Screen. The new events are listed on this screen.

Exit Code Check Error Handling

If a SYSOUT file read error occurs while the Monitor is trying to read the exit code from the job SYSOUT, this error will be treated as a temporary error. The Monitor will attempt to read the exit code up to 10 times. The time between the attempts is equal to the Monitor wait time. If there is still no success after 10 attempts, the job will be set to the status permanent error.