What's the difference between "static" and "dynamic" predecessors

book

Article ID: 49454

calendar_today

Updated On:

Products

CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Unicenter Job Management Option

Issue/Introduction

A new predecessor type of "static" was implemented in JMO r11.
All predecessor conditions implement prior to r11 are, by default, "dynamic."

From the Reference guide:
===================

Type

Indicates whether the predecessor is dynamic or static:

DYNAMIC
A dynamic predecessor is loaded into the tracking file only when the corresponding predecessor job or jobset is in the current-day workload.

STATIC
A static predecessor is loaded into the tracking file whether or not the corresponding predecessor job or jobset is in the current-day workload.

There are reasons for both to exist. Consider the follow example:

You have an "update" job and a "report" job.
The "update" job is a predecessor to the "report" job.

If the "report" job should run after the "update" job has run, when the "update" job is in the schedule, the predecessor type should be "dynamic."

If the "report" job should run after, but only if, the "update" job has run, the predecessor type should be "static."

Environment

Release: UWSMWL55500-11.2-Network and Systems Management-Job Management Option
Component: