Managing the Spooler Using Spoolcom
Guardian User’s Guide—425266-001
15-3
Managing Collector Processes
Managing Collector Processes
Adding a Collector to Your Spooler Subsystem
You might want to add a collector if:
•
The size of spooled jobs varies greatly
•
Your applications sometimes get file-system error 45 (DISK DIRECTORY IS
FULL)
Configuring several collectors with different unit sizes to handle the different types of
jobs results in a more efficient use of disk space.
You can add a collector to a spooler any time the spooler is not draining or dormant. It is
not necessary to stop the spooler to add a new collector. As soon as a new collector is
defined, the supervisor control files are updated with its name and attributes. If you want
the collector to be part of your configuration every time you system load the spooler,
add it to the spooler configuration file.
1. Define the collector:
> SPOOLCOM
) COLLECT $collector-name, DATA data-filename
[ , collector-attribute ] ...
Collector attribute subcommands are described in Table 15-2 on page 15-4.
2. If the spooler is in the warm state or cold state when you add the new collector,
enter:
) SPOOLER, START
3. If the spooler is already active when you add the new collector, start the collector:
) COLLECT $collector-name, START
Example
This example is based on these collector attributes:
•
The data file name is $SPOOL.SPOOLER.S2DATA.
•
The backup CPU is processor 2.
•
The processor that is to run this collector is CPU 3.
Topic Page
Adding a Collector to Your Spooler Subsystem 15-3
Displaying Collector Attributes 15-4
Modifying Collector Attributes 15-5
Deleting a Collector 15-5
To Next Page
Loading...
Need help?
General