Every bundle is a category in a printing mission. It is possible to use the standard runtime scheduling parameters in order to control the sequence by which bundles are printed. For example, if you specify higher priority for the couriers that have to leave earlier, they are printed before other bundles with lower priorities (for example, NORTH-COUNTY has higher printing priority than the SOUTH-COUNTY).
It is also possible to define mission dependencies using the prerequisite condition concept. For example: the 132PAPER mission for the management box starts printing only if the SOUTH-COUNTY/80PAPER mission has finished.
Printing missions can be triggered automatically or manually. Consider the following scenario:
The job that produces the report to be printed on blue paper has been decollated by Control-V.
The operator is notified with a highlighted, unrollable message to place the blue paper on the printer and to let Control-V know when the printer is ready. This is done using the Shout facility.
The operator places the paper in the printer, defines it for exclusive use by Control-V and starts the printer under Control-V (if it wasn’t already open). For more information, see the Control-D and Control-V chapter of the INCONTROL for z/OS Administrator Guide.
The operator enters the manual conditions list and specifies A (Add) next to the prerequisite condition BLUE-PAPER-READY. As a result, the printing mission starts executing.
