PERT View Flow Diagram Icons
What Is It?
The PERT View flow diagram shows the jobs in a schedule and the relationships between them. Each job appears as a rectangle (a job box) that contains a colored bar indicating job status, an icon representing the job type, the job name, and one or more information icons that flag special conditions such as dependencies, events, and threshold or resource updates.
Use the icons to read a schedule at a glance: the job type icon tells you what platform or technology the job runs on, and the information icons tell you why a job might wait, what it depends on, or what it updates when it completes.
For the colored status bar, see Setting Preferences for Status Colors. For job status descriptions, see Job Statuses in the Concepts online help.
Job Type Icons
The diagram can display any of the following job type icons:
| Icon | Job type |
|---|---|
 | BIS |
 | Container |
 | File Transfer |
 | IBM i |
 | Java |
 | MCP |
 | Null Job |
 | OpenVMS |
 | OS 2200 |
 | SAP BW |
 | SAP R/3 and CRM |
 | SQL |
 | Tuxedo ART |
 | UNIX |
 | Windows |
 | z/OS |
Information Icons
The diagram can also display any of the following information icons:
| Icon | Meaning |
|---|---|
 | The job has a circular dependency. |
 | The job has an event. |
 | The job has a dependency on a job in another schedule. |
 | The job has a dependency on another schedule date. |
 | A job required by this job is missing. |
 | The job has an expression dependency. |
 | The job has a threshold or resource update. |
FAQs
Why does a job show more than one icon?
A job box shows a job type icon together with any information icons that apply, so a job can display several icons at once, for example a job that has both an event and a dependency on another schedule. What is the difference between the three dependency icons?
Each dependency icon represents a different relationship: a dependency on a job in another schedule, a dependency on another schedule date, and a job required by this job that is missing.
Glossary
Container Job: A job type that runs a subschedule. Container jobs enable hierarchical schedule structures and support properties and events just like standard jobs.
Null Job: A job type that runs no work on any platform. Null jobs are used to hold dependencies, trigger OpCon events, and keep schedules open after all other jobs complete.
Threshold: A numeric variable stored in the OpCon database used to control whether a job runs. Jobs can be made dependent on threshold values, and OpCon events can update threshold values at runtime.
Resource: A numeric variable in OpCon representing a finite pool. Jobs can be configured to require a set number of resource units to run, limiting concurrent runs and preventing resource contention.
Schedule: A named container for jobs in OpCon, built for a specific date to create that day's automation. Schedules define build settings, frequencies, and the jobs that run within them.
Job: The fundamental unit of work in OpCon. A job defines what to run, on which machine, when to start, and what conditions must be met. Job results are tracked and can trigger events and notifications.