Previous Topic

Next Topic

Book Contents

Book Index

Workload Constraints

We have discussed previously under Printing Methodologies, that Control-D prints output differently from the first-come-first-serve basis that occurs in a manual system. With Control-D, ideally we want to print all reports for a user in one printed bundle.

However, this means that you have to wait until all reports for the user have been created before you start printing. This may be impractical if you have a series of lengthy batch jobs producing high volume reports. It may be that by the time the last reports for a user are created, there is not enough time to print all the users reports to meet the dispatch deadlines.

In this case, it may be necessary to set up multiple bundling runs at different times, for example, bundle up all reports for Branch 11 at 2200 and again at 0300. This way, you can be sure you have enough time to print all the created output. The hours set for bundling runs depend on the workload and practices of your site.

We will modify the category names of our sample printing missions to cope with this situation where required:

Table 28 Splitting Bundles into Multiple Runs - Example

New Category Names

Processing Description

MIAMI-BRANCH-RUN1

First bundle for Miami at 2200

MIAMI-BRANCH-RUN2

Second bundle for Miami at 0300

DALLAS-BRANCH-RUN1

First bundle for Dallas at 2300

DALLAS-BRANCH-RUN2

Second bundle for Dallas at 0430

Parent Topic

Printing Mission Naming Standards