RE: Undeleteing a spoolfile

Bill,

I can't speak to your direct experience, but it does contradict the
characteristics of the RCLSPLSTG command.  On a stable system, one on
which the number of spool files stays relatively constant; the command
will have very little benefit.

Spool file data is stored in physical file members in the QSPL library.
If I recall correctly, each physical file has 1,000 members.  When a
spool file is deleted from an output queue or finishes printing with
SAVE(*NO), then that member is cleared.  To lessen system overhead,
these members are reused constantly.  The RCLSPLSTG command removes
those members from the physical files which have been empty for the
specified number of days.  I would use the command when you have had an
abnormally large number of spool files on your system and then they are
gone.  It will remove those empty members.

If you feel like poking, you could look at the characteristics of the
files by signing on with *ALLOBJ authority and then using PDM in the
QSPL library.  You should find some empty members which consume very
little storage.  Look only if you do this!  :)

Regards,
Andy Nolen-Parkhouse

> This was not my experience on a V4R4 (V4R5?) system.  Batch job
entered a
> loop
> and was spitting out job logs consistently until we stopped it.  A
couple
> thousand job logs were deleted and we did not regain the disk space
until
> the
> spool storage was reclaimed.
>
> Also, if the system were to run as you suggest, then what would be the
> purpose
> of the reclaiming storage command?
>
> Bill