Defining Requirements › Predecessor and Successor Definition › DB.3.4 - Input/Output Network Tasks 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.

The combination of job name, job schedule ID, network name, and network sub-ID handles any unique variations of a network connection.

A connected input network becomes a requirement for the job. An input network connection is not considered a true requirement for the following conditions:

• A RUN or LOAD command scheduled the job.
• The requirement does not apply to this run (schedule ID dependency).
• The requirement was defined as NEXT-RUN=SKIP.
• The job was DEMANDed using TYPE=RES.

A connected output network is scheduled into the postprocess queue when the job enters the request queue. After the network is defined with the DB.5 panel, the network is logically connected to one or more jobs with the DB.3.4 panel. (Required scheduling parameters must also be entered with the DB.2.3 panel. The schedule, however, is not RESOLVed.)