Spooler Utilities Reference Manual

SPOOL Program
Spooler Utilities Reference Manual—522295-003
A-3
Running the SPOOL Program
num-of-print-processes
is the maximum number of print processes that will be declared for this spooler.
The range is 1 through 45. There is no default.
num-of-fonts
is the maximum number of font jobs that will ever be declared for this spooler.
The range is 1 through 255. The default is 16.
num-of-batch-jobs
is the maximum number of batch jobs that will ever be declared for this spooler.
The range is 1 through 4095. The default is 256.
num-of-device-queue-nodes
is the maximum number of device queue nodes. Every job needs a minimum of
1 device queue node. The optimum value of this parameter is twice the number
of jobs. The default value is 131086.
R[EBUILD]
is used during a warmstart to specify new coldstart parameters or to recover from
control-file corruption. cold-start-parameters must be specified when you
use this option. See Considerations for more information.
Considerations

The supervisor forms the names of its control files by appending digits from 0
through 9 to the specified control-filename.

When cold starting a spooler, make sure that none of the control-filename
files exist, because the supervisor attempts to create them. If a file already exists,
the supervisor will fail and terminate. The spooler might not use all of these files,
but you should keep them reserved for use by the spooler.

You must specify NAME $supervisor-process, because the spooler will not run an
unnamed process. It is recommended that you use $SPLS as the name for the
spooler supervisor. Running SPOOLCOM without specifying a particular
supervisor causes SPOOLCOM to communicate with a process named $SPLS.

The process name assigned to a supervisor on a warmstart need not be the same
as the process name assigned to the supervisor the last time the spooler was
made active. It is the control file name rather than the supervisor process name
that uniquely identifies a particular spooler.

The REBUILD option causes the supervisor to rebuild the spooler control files.
One symptom of a corrupted control file is a corrupted job map. This can be seen
if you warmstart a spooler and find a listing for a job 0 when you execute the JOB
command (indicating that the new spooler has a corrupted job map).