Use of Jobs

#### Search Results

Search

# Use of Jobs

All jobs are members of job networks and can be linked by logical conditions. Some differences arise in End-of-Job checking, depending on the job type and the operating system (see the section Defining and Managing End-of-Job (EOJ) Checking and Actions). However, you can always define `Job OK` or `Job not OK` as a condition for subsequent system action.

An operating system job on z/OS can consist of several steps. In these cases, Entire Operations can check the result of each job step as part of End-of-Job analyses and triggers system action accordingly.

A job is uniquely identified within a job network by its job name. The job name can, but need not be the same as the JOB or LOGON statement name (job name by which the operating system identifies the job). Before job submission, jobs can therefore only be identified by the name defined to Entire Operations. A job can only be accessed through Entire Operations by its Entire Operations name.

When defining a job, you must also specify:

- JCL location (depending on job type);

- JCL and execution nodes (if different from those specified for the job network);

- JCL and submit user IDs;

- Scheduling parameters (optional; otherwise, the network default is used);

- End-of-Job checking and End-of-Job action specifications (see the section Defining and Managing End-of-Job (EOJ) Checking and Actions for details).

Note for z/OS:

We recommend that the JCL of one Entire Operations job contains only one job statement. Entire Operations retains only the first job number assigned to a submitted job.