Guardian User's Guide

Performing Routine Spooler Operations Using

Spoolcom

Guardian User’s Guide—425266-001

14-12

Starting a Drained Spooler

Warmstarting a spooler is theact of bringing the spooler from the warm state to the

active state. When the spooler is dormant, the supervisor is not running. As soon as you

create another supervisor process, the spooler enters the warm state. When you

warmstart the spooler, you use the same control files and other files that were in use

when the spooler was previously drained.

Coldstarting a spooler is the act of starting a new spooler. When you coldstart a spooler,

you create new control files in which the collectors store jobs (when you warmstart the

spooler, the collectors use existing control files).

The key distinction is that in a coldstart the supervisor is run with a new control file,

while in a warmstart the supervisor is given the name of an existing control file. Before

you coldstart your spooler, you must purge all existing supervisor control files. The

coldstart process creates new control files. Any jobs waiting in the current queue file are

purged during a coldstart, and users must respool these jobs after the coldstart finishes.

Warmstarting a Drained Spooler

1. Log on as a super-group user (255,n), but not as the super ID (255,255).

2. Run the spooler supervisor, supplying the name of an existing spooler control file:

> SPOOL / IN control-filename , NAME $supervisor-process /

See the Spooler Utilities Reference Manual for a description of the SPOOL

program.

3. Optionally add, delete, or modify collectors, print processes, devices, and routing

structures (see Section 15, Managing the Spooler Using Spoolcom

4. Start the spooler:

> SPOOLCOM SPOOLER, START

Note. If you are warmstarting the spooler after migrating from one system version to

another, see the migration considerations in the Spooler Utilities Reference Manual.