Logical conditions are dependencies between jobs. They are defined using the logical conditions maintenance facility. A logical condition can be added, deleted or modified. Any number of logical conditions can be assigned to any one job. A logical condition can have either of two statuses that determine how Entire Operations is to continue processing: TRUE (condition exists) or FALSE (condition does not exist).
All conditions are identified by name and a reference date to allow the Entire Operations Monitor to distinguish between the same event occurring on different dates. Dates can be specified as relative dates or explicit dates. All relative dates are converted to real dates when the job is put in the active queue. See also Date and Time Formats in the User's Guide.
There are two ways of using logical conditions:
as input conditions;
This document covers the following topics:
Input conditions must be fulfilled before Entire Operations can submit an active job. In order to link two jobs, an input condition must also be defined as an output condition for the preceding job. An input condition can be fulfilled by a CPU event or manually by the user.
16.02.15 ***** Entire Operations ***** 16:53:19
+-------------------------------------------------------------+
Owner E | |
| Master Input Condition Modification |
-------- | | ------
C Condi | Owner ==> EXAMPLE___ | it
M E60-J | Network ==> B60-FLOW__ Version ==> |
_ EX-2 | Condition ==> E60-JOB2-O1_________ Run ==> _____ |
_ EX-3 | Reference ==> RUN_____ |
_ E05-U | |
| Usage (mark with Y or N) |
| Must Exist: Y Exclusive: _ Destroy after usage: _ |
| Activation Mode ==> N |
| |
| Depending on |
| Exit ==> _ Multiple Suffixes ==> _ |
******* | File Existence ==> _ Mailbox ==> _ | ******
D Delet | User Sw.(BS2000) ==> _ Symbol Value ==> _ |
| Job Var.(BS2000) ==> _ |
| |
Command | -PF1---PF2---PF3-------PF5------------PF9---PF10---PF12-- |
| Help Add End Save Xref ScDep Menu |
+-------------------------------------------------------------+
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Add End ACond Save Up Down Menu |
Apart from a name and reference date, the user can also assign a mailbox to a condition. Each user ID can also be associated with up to 10 mailboxes. Entire Operations will automatically notify each user of all pending conditions assigned to any mailboxes associated with his user ID.
The user can also further specify what status the condition should be in before the job can be submitted (TRUE or FALSE), whether this job must wait until the condition applies exclusively to it (e.g. to prevent parallel running of two or more jobs with the same input condition), and whether Entire Operations is to automatically reset the condition after job submission.
Before job submission, all input conditions defined for the job are checked automatically by the Entire Operations Monitor. If you want the checking to be done by a Natural user exit this routine must also be specified in the input condition definition screen.
For detailed information, see the section Defining and Managing Job Input Conditions in the User's Guide.
Output conditions will be maintained automatically by the Entire Operations Monitor if their associated events have occurred. In this case all jobs will be started which have these conditions as input conditions. Events and output conditions are defined within Entire Operations end-of-job checking (see the section End-of-Job Checking).
16.02.15 ***** Entire Operations ***** 16:44:22
Owner EXAMPLE Network B60-FLOW Version Job JOB-01
End-of-Job Checking + Actions MVS/ESA Run Date
------------------------------------------------------------------------------
C Action +---------------------------------------------------------+ s OA
C C | | k
| Occurrence of String 'INVALID RESPONSE-CODE' |
| Output Conditions |
| Cmd State Condition Name Reference Run |
| _ Set E60-JOB1-O RUN |
| _ Set E60-JOB2-02 RUN |
| _ Reset E60-JO15-0 RUN |
| _ Reset E60-JO19-0 RUN |
************* | _ Reset E60-JOB1-0 RUN | ****
_ C | |
_ | |
------------- | | ----
A Activat. C | | ther
P Descr. R Re | | Set
| D Delete M Modify W Where used |
Command => __ | Enter-PF1---PF2---PF3---PF5-------PF7---PF8----PF12- |
| Help Add End Save Up Down Menu |
+---------------------------------------------------------+
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Add End Save Up Down Menu |
As in the case of input conditions, output conditions are defined by name and reference. Additionally, the user can specify whether the output condition is to be set (to TRUE) or reset (set to FALSE) when the associated event occurs.
Up to 20 output conditions can be associated with a single event.