Previous Topic: Input NetworksNext Topic: IN Command Response


Output Networks

When a job is placed in the request queue (by demand or automatic schedule), all output networks defined for that job's output (using DB.3.4 panel) are placed in the postprocess queue.

All output networks connected to the job (through DB.3.4 panel) are assigned the same CA 7 job number used to identify the job in the request queue. This job number must be used by each workstation, except the first, to log the start and completion of its activity. Since multiple output networks can exist for a single job (and job number), network information, SUBID information, or both must also be used when logging starts or an activity completes.

Workstations within a network must log in and log out in their defined sequence. Only one workstation at a time can be logged in for a given network. A single workstation can be logged in to more than one network at the same time. Each workstation must log in before it can log out. A workstation cannot log in until the preceding workstation in the network has logged out (for that activity).

A workstation can be prompted for an activity that has already been completed if CA Workload Automation SE was not properly notified of the completion. LOGIN and LOGOUT commands should be used in response to the prompt to notify CA Workload Automation SE of task completion. You can use the IN Command Response in place of LOGIN. The IN top line command is used to indicate the beginning of a workstation task. The IO command in this section can be used to log in and log out with a single command.

If the same station is defined in a network more than once, LOGIN and LOGOUT should not be used.

More information:

IN Command Response