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

This document covers the following topics:

Field Descriptions: Add/Modify Event Definition

Field Descriptions: Add/Modify Event Definition

(z/OS, z/VSE)

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.
	C	Return code received during job execution (job step). See Example of a C-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. Notes: All checks of the SYSOUT file and actions, which refer to the SYSOUT file, are not executed, if no SYSOUT file exists. This case will apply, if the job is submitted as a temporary dummy job. A string search in a non-existent file is handled like "string not found" in an existing file.
Step Name	(for a C-type event) The JCL step to be checked for the return code specified in the Operator and Event Type fields.
	Special step names:
	/ANYSTEP	Event occurs if the definition is true for any step of the jobs.
	/MAXCC	Event occurs if it is true for the maximum termination code (condition code) of the job.
	Note: In z/VSE you can define STEPNAMEs for Entire Operations with the LABEL statement: /.label, where label stands for STEPNAME. The STEPNAME defined in this way is valid for the following EXEC statement.
Operator	(for a C-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	Code is equal to specified value.
	>= or GE	Code is greater than or equal to specified value.
	> > or GT	Code is greater than specified value.
	<= or LE	Code is lower than or equal to specified value.
	< or LT	Code is lower than specified value.
	<> or NE	Code is different from specified value.
Event	(for a C-type event) Specify a condition code to be compared with the return code. Possible values:
	Cxxxx	Condition code xxxx (z/OS) Return code xxxx
	Sxxx	System abend code xxx (z/OS only)
	Uxxxx	User abend code xxxx (z/OS only)
	JNR	Job not run, JCL error. Note: If this event occurs, and a JNR event definition with OK exists, this can be treated as ok. See also z/OS Defaults for Event Checking.
	JFL	Job failed, JCL error. Note: If this event occurs, and a JFL event definition with OK exists, this can be treated as ok. See also z/OS Defaults for Event Checking.
	JDL	Job deleted by operator.
	JIR	Job execution interrupted (for example: system crash)
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)
Exit Mode	'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.
missing	String missing: If "Y" is defined here: If the string is not found, the event will be satisfied.
Select (z/OS)	You can limit the search for strings by specifying file numbers in this field according to file type (SM, SO, JL). Enter file type followed by number, range of numbers or an asterisk * as wildcard. For example:
	SM 1	Search system messages 1.
	SM 1 5	Search system messages 1 to 5.
	SO*	Search all SYSOUT files.
Select (z/VSE)	You can use these file types: LST, PUN, RDR.
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: 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).