Spooler Utilities Reference Manual
RPSetup Utility
Spooler Utilities Reference Manual—522295-003
6-7
Requirements for Running RPSetup
If you use a print process other than FASTP, you must ensure that the default
values of the configuration parameters are appropriate for the print process you
use. Because the default configuration parameters are set for the FASTP print
process, you might need to specify PARAM commands to set configuration
parameters specifically for the print process you use. For some default operations
performed by FASTP, see PARAM DEVPARM
on page 6-13. For all the
configuration parameters of print processes, see the DEV command.
Default values for RPSetup are set with the assumption that the FASTP print
process retains the source job location and job ownership when the job is copied to
the target spooler, but that FASTP omits any HOLDAFTER flag for a transferred
print job. For information about controlling FASTP default operation, see PARAM
DEVPARM on page 6-13.
Setting up more than one thread between two spooler systems provides more
efficient use of any Expand connection than a single thread would. The number of
threads equals the number of print jobs that can be simultaneously transferred to a
remote spooler. The PARAM NUMTHREADS command controls the number of
interspooler threads configured (the default number is 2).
Requirements for Running RPSetup
These are the requirements for running the RPSetup utility:
You must either be a system operator (user ID 255, n) or be the owner of the local
spooler processes.
You must have a remote password and be able to logon to the remote system.
If remote-spooler is protected by the Safeguard security facility, your user ID
must meet Safeguard requirements to access remote-spooler.
Before issuing the RPSetup command, you must issue ASSIGN and PARAM
commands for configuration parameters whose default values are not appropriate
for your spooler.
You must run the RPSetup utility on the local node to access and change spooler
configuration files.
The remote spooler must have at least one collector in the active state.
remote-spooler and local-spooler are usually on different nodes of an
Expand network, with one rare exception. Occasionally, both spoolers will be on
the same node when there are more devices than a single spooler can support.