What are the advantages of SpoolMate processing and controlling spool files at the copy level?
There are many advantages: • Each copy is handled as a separate print task with its own set of processing parameters, which allows flexibility in printing different jobs. • Different copies of the same spool file can be queued at different priorities, printed by different devices, on different stationery, with different banners and even on different CPUs in the network thereby providing flexibility for print jobs and allocation of workload to be distributed. • Spool file copies can also be transferred between MPE and UNIX systems via TCP/IP.
Related Questions
- Can TM be configured to only copy files from a specific top level directory such as ~/Documents or ~/Library/Mail? Can it be configured to only copy files from multiple such folders?
- What advantages/disadvantages are there to having redundancy at the broker, rather than node, level?
- What are the advantages of SpoolMate processing and controlling spool files at the copy level?
