Defining Requirements › Predecessor and Successor Definition › DB.3.1 - Data Set Predecessors Panel › Usage Notes

Usage Notes

You can add more requirements on a one-time basis. You can skip existing requirements on a one-time basis.

A data set connection is not considered a true predecessor requirement when any one of the following conditions are true:

• The data set is TYPE=PERM on DB.6 panel.
• The requirement is marked PERM for this job on the DB.3.1 panel.
• The job is marked MAINT=Y on the DB.1 panel.
• The requirement does not apply to this run (schedule ID dependency).
• The requirement was defined as NEXT-RUN=SKIP.
• A RUN or LOAD command scheduled the job.
• The job was DEMANDed using TYPE=RES.

The combination of job name, job schedule ID, and data set name handles any unique variations of the data set connection.

If the LOADDSNS keyword is used on the DBASE statement in the initialization file, then the LOAD process does not build any DD or data set information for jobs that are marked MAINT=Y on the DB.1 (JOB) panel. The result is that there are no data set connections for these jobs unless added they are added manually.