Xerox Paris, a document system Support & Software User Guide
Chapter 2
The PARIS Spooler32 Technical Manual
42
Overview of ‘Directory’ as the Input Source
If this is the first time you are defining a directory as an input source, it is
important that you understand the way the Spooler generates its processing
requests and what it does when polling directories for input data.
important that you understand the way the Spooler generates its processing
requests and what it does when polling directories for input data.
How the Spooler polls Directories for Input Data
Each time a file is found that matches the directory search path criteria, the
Spooler performs two actions. One, it creates an SJR or Spooler Job Request
and two, the input is tagged as either hidden, or the file name is changed
Spooler performs two actions. One, it creates an SJR or Spooler Job Request
and two, the input is tagged as either hidden, or the file name is changed
or the
file extension is changed
according to what has been selected in the
View/Change Directory Search Settings dialogue (refer to
Defining the
directory search settings on page 46).
Spooler Job Requests (SJR)
The SJR is the mechanism by which the Spooler passes instructions to the
formatting engine. It contains all the information the engine needs to
successfully process the job and deliver the output to its final destination.
formatting engine. It contains all the information the engine needs to
successfully process the job and deliver the output to its final destination.
A Spooler Job Request is exactly as the name implies, that is, a request from
the Spooler to the engine to process a job. The Spooler Job Request remains
until the engine has completed the request and sends notification back to the
Spooler that the job has been completed.
the Spooler to the engine to process a job. The Spooler Job Request remains
until the engine has completed the request and sends notification back to the
Spooler that the job has been completed.
Once the engine notifies the Spooler it has completed processing, the input file
is then deleted. This means that if the system is shut down while job requests
are still in the queue, when the Spooler is next opened those job requests would
still be queued awaiting processing. It also means that if the data file for the
request is deleted before it is processed, the request will remain forever or until
manually deleted.
is then deleted. This means that if the system is shut down while job requests
are still in the queue, when the Spooler is next opened those job requests would
still be queued awaiting processing. It also means that if the data file for the
request is deleted before it is processed, the request will remain forever or until
manually deleted.
Spooler Job Requests (.SJR) are stored in the \PARIS\SPL\0 sub directory.
When created they are given a generated number as a file name and only exist
until the engine has processed the file. An .SJR file is a text file that contains all
the information the engine needs to be able to find, process and deliver the file
for printing.
When created they are given a generated number as a file name and only exist
until the engine has processed the file. An .SJR file is a text file that contains all
the information the engine needs to be able to find, process and deliver the file
for printing.