I have just started archiving spool files by changing our print command
files to SPSAVE every one as it's printed, so that the spool file will be
present when the nightly backup is run.  After being backed up to tape, the
spool files are purged.  The problem is that the STATE column of the SHOWOUT
command still displays READY after a file has been printed and SPSAVE'd,
causing users to think their print command did not take and that they need
to try again.  Almost all our spool files are created by the batch user
JOBS, so that JOBS is the creator of the file.  This means the person who
streamed the job, unless they have a capability such as AM, cannot use the
LISTSPF command to list any spool files.

I made a command file that uses an MPEX flexible LISTF format to display the
necessary information, but the performance of this command file is very
poor.  It sometimes takes over 5 seconds to execute.

As far as I can tell, the FINFO function does not distinguish between a
spool file in the READY state and one in the SPSAVE state.

How else might I report back to the users that a spool file is in the SPSAVE
state?

Nicholas Saner
Gaiam, Inc.
(303) 222-3656