Xerox Paris, a document system Support & Software User Guide
Appendix E: Spooler Preprocessing
The Paris Spooler Technical Manual
232
Important points to know about using Preprocesses
If preprocessing results in the creation of a fully formatted print file…
If any of the preprocessing steps result in the creation of a fully formatted print
file, then the final file should not be processed by the Paris Engine. The ‘default
environment’ name for this job should be set to ‘<NONE>’, which tells the Paris
engine to simply pass the resulting file through to the final printer, without
examining it.
file, then the final file should not be processed by the Paris Engine. The ‘default
environment’ name for this job should be set to ‘<NONE>’, which tells the Paris
engine to simply pass the resulting file through to the final printer, without
examining it.
The Xes2Ps application is an example of this, where the output file is a fully
formatted PostScript print file. The Paris Spooler passes this to the Engine, which
should not attempt to further process the file. (See ‘Example of how to run an
application as a Preprocess’ on the following page.)
formatted PostScript print file. The Paris Spooler passes this to the Engine, which
should not attempt to further process the file. (See ‘Example of how to run an
application as a Preprocess’ on the following page.)
If the preprocess uses the redirection operators ("<" and ">") for I/O…
If the preprocess to be run is a program that uses the redirection operators ("<" and
">") for I/O, such as XES2PS.EXE, then it is necessary to place the command and
parameters in a command file or batch file, and set the Paris Spooler to call the
command/batch file. This sidesteps a limitation in the WIN32 ‘CreateProcess’
API.
">") for I/O, such as XES2PS.EXE, then it is necessary to place the command and
parameters in a command file or batch file, and set the Paris Spooler to call the
command/batch file. This sidesteps a limitation in the WIN32 ‘CreateProcess’
API.
If you wish to run multiple copies of the same preprocess
simultaneously…
If you wish to run multiple copies of the same preprocess simultaneously (that is,
the preprocess is a program that can run multiple instances, and each instance does
not conflict with any other in terms of shared resources, etc.) then the user must
create multiple preprocess definitions within the Paris Spooler.
the preprocess is a program that can run multiple instances, and each instance does
not conflict with any other in terms of shared resources, etc.) then the user must
create multiple preprocess definitions within the Paris Spooler.
Each definition has a unique name, but the same ‘command’ details. The user then
creates separate job definitions, each of which uses a unique preprocess definition.
creates separate job definitions, each of which uses a unique preprocess definition.