You can define output conditions for an event or a job.

This document covers the following topics:

• Adding Output Conditions for an Event

• Adding Output Conditions for a Job Event

• Fields and Columns: Output Conditions

---

Adding Output Conditions for an Event

To add an output condition definition for a defined event

1. Type C in the line command field of the selected event on the End-of-Job Checking and Actions Screen. Press Enter.

   The Output Conditions window opens with a list of existing output conditions).

2. Proceed as described after Column Headings: Output Conditions in the subsection Adding Output Conditions for a Job Event.

Adding Output Conditions for a Job Event

You can define a condition at the job level according to End-of-Job status (job ok = All checks ok, job not ok = Any check not ok).

To do that

1. Type the C line command in the All checks ok or Any check not ok line command field on the End-of-Job Checking and Actions Screen.

2. Press Enter.

   The Output Conditions opens with a list of existing output conditions:

   24.10.08 ***** Entire Operations ***** 15:07:09 Owner EXAMPLE End-of-Job Checking + Actions MVS/ESA Job JOB-02 Network E60-FLOW Run Date ------------------------------------------------------------------------------ C Action +---------------------------------------------------------+ OA _ P ! ! _ ! Job ended ok ! _ ! Output Conditions ! _ ! Cmd State Condition Name Reference Run ! _ ! _ Set E60-JOB2-O1 RUN ! _ ! _ Set E60-JOB2-O2 RUN ! _ ! _ Reset E60-J015-O RUN ! _ ! _ Reset E60-J019-O RUN ! ************* ! _ Reset E60-JOB1-O RUN ! **** c C P ! _ ! _ PR ! _ ! ------------- ! _ ! ---- A Activation ! _ ! ther P Descr. R Re ! _ ! Rtn ! D Delete M Modify W Where used ! Command => __ ! Enter-PF1---PF2---PF3---PF5-------PF7---PF8----PF12- ! Enter-PF1---PF ! Help Add End Save Up Down Menu ! 2--- Help Ad +---------------------------------------------------------+ u

Fields and Columns: Output Conditions

• Field Descriptions: Output Conditions

• Column Headings: Output Conditions

Field Descriptions: Output Conditions

Field	Description
Condition	Condition name. Symbol replacement is possible. The submission escape character is to be used.
		A condition that can be used across networks is called a global condition. If you want to add or modify a global condition: The prefix is the plus sign (+). A global condition is assigned to the SYSDBA owner and network.
Reference	An output condition can be set with different references (usually the current network run number). Possible values:
	RUN	Current run number of the job network is assigned. This is the default.
	ABS	Absolute condition. Exists only once, because it is independent of run numbers.
	RCM	Sets an active condition with owner, network, run number of calling network and appends multiple suffixes. RCM can be used to determine that the conditions defined for a predecessor job apply to all jobs that reference this predecessor in multiple activated subnetworks. In this case, the input condition of the corresponding successor job must be referenced with RCA: see RCA in the section Possible References for Input Conditions.
	The reference is evaluated and set when the active condition is created by the Monitor according to the End-of-Job definition.
Run	Run number of job to which this condition is to apply when modifying condition for an active job. Default is a blank character.
State	Determines whether the defined output conditions must be met if the associated event occurs. Possible values:
	SET	The specified conditions must be met. This is the default.
	RESET	The specified conditions are ignored.

• Press PF3 (End) to save the definition and return to the list of conditions in the Output Conditions window.

You can define up to 50 output conditions for any one event at the job step level, or at the job level according to All checks ok and Any checks not ok.

Column Headings: Output Conditions

Column	Description
Cmd	One-character line command input field. Possible values:
	D	Deletes condition as output condition for the job.
	M	Modifies the output condition definition.
	W	Displays a table of jobs for which this condition is defined as input or output condition. For more information, see the subsection Displaying Output Condition Use.
State	A condition can be set (to TRUE) or reset (to FALSE) on the occurrence of an event.
Condition Name	User-defined name for condition. Use this name if you wish to define this output condition as an input condition for another job.
Reference	Notation used to distinguish between the same condition in different job runs. Use this reference date if you wish to define this output condition as input condition for another job. If left blank, the current run is assumed.
Run	Run number of job to which this condition applies when modifying condition for an active job.

To add an output condition definition

• Press PF2 (Add).

  The Output Condition Addition window opens:

  24.10.08 ***** Entire Operations ***** 15:11:33 Owner EXAMPLE End-of-Job Checking + Actions MVS/ESA Job JOB-02 Network E60-FLOW Run Date ------------------------------------------------------------------------------ C Action +---------------------------------------------------------+ OA c P ! ! _ ! Step STEP1 returns Condition Code = C0000 ! _ +-------------------------------------------------------+ ! _ ! ! n ! _ ! Step STEP1 returns Condition Code = C0000 ! ! _ ! Output Condition Addition ! ! _ ! ! ! _ ! Condition ==> ____________________ ! ! ******** ! Reference ==> ________ ! ! **** _ C P ! Run ==> _____ ! ! _ PR ! Set/Reset ==> _____ ! ! -------- ! ! ! ---- A Activa ! PF1 Help PF3 End PF5 Save ! ! ther P Descr. +-------------------------------------------------------+ ! Rtn ! D Delete M Modify W Where used ! Command => __ ! Enter-PF1---PF2---PF3---PF5-------PF7---PF8----PF12- ! Enter-PF1---PF ! Help Add End Save Up Down Menu ! 2--- Help Ad +---------------------------------------------------------+ u