Skip to content
  • There are no suggestions because the search field is empty.

Explore - Jobs Tab

The Jobs tab lists batch jobs ingested with the project from job languages—JCL on z/OS and CL, CLLE, and related control language on IBM i (including AS/400-based applications). Use it to understand batch orchestration: which steps run which modules, which data sets move data in and out, and how jobs connect to variables that represent file records.

Zengines processes jobs that run COBOL, RPG, PL/I, and other supported legacy modules on IBM systems.

Job grid

Each row is one job. Summary columns often include:

  • Number of steps
  • Number of modules invoked
  • Number of data sets

These counts help you compare job complexity the same way table read/write counts help on the Modules tab.

Filter by module

Filter the jobs list by module to answer: “Which jobs run program X?” That narrows a long job catalog to the batch paths relevant to one program.

Job detail

Select a job to see:

  • Steps in execution order
  • Links to data set names and logical files
  • Links to modules executed in each step
  • Links to variables that represent records on files used in the job

A common pattern: identify the job that extracts or loads data, open the step that runs your module, follow the link to the variable that models the file record, then continue lineage on the Variables tab. On the variable detail view, check the variable tree for hardcoded values next to variable names when literals are resolved in code.

Zengines Assist - Job Summaries

On the job detail view, use the same workflow as modules and variables:

  1. Click Summary for a short overview of what the job does in business terms.
  2. Click Tell Me More for deeper functional and technical narrative, with hyperlinks into modules, files, variables, and related items.
See Zengines Assist - Job Summaries.

Jobs and project completeness

Jobs are not required to create a project, but including job language sources (JCL, CL, CLLE, and related) greatly improves file linkage and batch context. Without jobs, rely more on table/SQL lineage and module-level file sections where job definitions exist for individual programs.