This document covers the following topics:
If a symbol replacement error occurs at submission time, the event JNR "Job not run - JCL error" will be set to "occurred".
If the event JNR is not defined, it will be added to the active job.
If no events are defined for a job, Entire Operations provides a default check of the return code type (for a C-type event):
If a system code unequal to 0 (zero) has occurred at any job step, the job is evaluated as not ok if this event is not explicitly defined. This also applies, if an event has occurred which has been defined using ANYSTEP. The occurrence of such an event has the priority over definitions, which apply for any steps.
It can be defined throughout the system, how the occurrence of the message IEF201I job terminated because of condition codes is treated (see Entire Operations Administration Documentation). If it was defined there that this message shall not default to not ok as a consequence, then this is written to the log, the job set to the status Job interrupted, and the job is treated as not ok. If this was not defined, then the occurrence of IEF201I in SYSOUT has no consequences.
If the message IEF287I data set not cataloged is received, it is written to the log and the job is treated as not ok.
If a condition code or user code, which is not explicitly defined, is received at any job step, it is compared with the highest value accepted as ok. The job is not ok if the code is higher than this default. The job is also not o , if no explicit check has returned an ok. For more information, see the subsection Entire Operations Defaults in the section System Administrator Services of the Entire Operations Administration Documentation.
If a string defined in the Global Message Code Table is found anywhere in the SYSOUT, its severity equivalent is compared with the highest condition code value accepted as ok. The job is not ok if the severity equivalent is higher than this default.
Events like JCL error, Job not run, Job interrupted cause the status "not ok" by default. Dedicated event definitions can override this.
In all other cases, the job is accepted as ok.
If a /MAXCC or /ANYSTEP check has been defined, and this event occurs, no check is done on the highest value accepted as still OK
/MAXCC precedes /ANYSTEP.
The same rules as for z/OS defaults apply to z/VSE.
Note:
No system codes are available in the z/VSE operating system.
The following messages lead to a not ok status of the z/VSE job:
PROGRAM ABEND
ENDED ABNORMALLY
OPERATOR CANCEL
In z/VSE SYSOUT the following date formats are recognized and handled:
| American Format | MM/DD/YY, MM/DD/YYYY |
|---|---|
| European Format | DD/MM/YY, DD/MM/YYYY |
If a date contains a 2-digit year specification in SYSOUT, then Entire Operations adds the century for further processing. In this case, a sliding window of + / - 50 years is applied.
Entire Operations either uses a defined Monitor job variable for a job or creates its own job variable, if job variables are available.
If the Monitor job variable displays an abnormal end, the job is not ok.
By default, if defined message keys appear, the job is regarded as faulty and is set to not ok: These message codes (see Defaults for BS2000) in the Administration documentation) are default settings which are in effect after the installation of Entire Operations. However, they can be deliberately adapted. It is possible to completely delete this table.
Please note each time this table is modified that possibly faulty jobs may not be set to not ok any longer. This list can be changed.
If messages like program dump, etc. appear in the SYSOUT, the job is not ok.
The Global Message Code Table is checked as described for z/OS, above.
In all other cases, the job is accepted as ok.
Entire Operations inserts start and end messages (EOR0301, EOR0302) in the SYSOUT.
If the end message EOR0302 is missing, the job is treated like an interrupted job. Because it is possible that the SYSOUT of an asynchronous child processes is written behind the end message, the message EOR0302 will be searched in the whole SYSOUT file. If the End-of-Job checking detects that there is unexpected SYSOUT behind the end message, the process times for accounting cannot be obtained. A note is being written to the log:
Process times for accounting not found ... SYSOUT of background processes may exist.
The Global Message Code Table is checked, as described for z/OS.
If no special event checking was defined for a job (UNIX and Windows), then the event is compared to a system-wide default value for UNIX or Windows. Depending upon this check, the job result can be set to not ok.
In all other cases, the job is accepted as ok.