Jim Riedel ([log in to unmask]) wrote:
: Problem:  I have a single file in my out list which remains in a
: "CREATE" state, and seems to be blocking any other out jobs from
: printing to the same printer.  This file has been in a "CREATE" state
: for about 24hours, which is unlikely to be a valid output (most of ours
: are done within an hour).  Does anyone know how I can get rid of this
: file?? When I try a SPOOLF; #Ojobnum;delete, I am told I cannot delete a
: job in creation state, yet it seems as though it may never complete...
: and is holding up all other output... Any help would be greatly
: appreciated...

Files in the CREATE state do not block other files, to the same printer or
to different printers.  If you are observing this behavior, something else
is happening, for example, if a process is blocked while holding a spooler
semaphore resource (SPFDIR, SPIT, possibly the JMAT).

You can't delete a file in the CREATE state because it is the output
file of the process creating it.  You must abort that process by
aborting the job it runs in.  If the spool file is a $STDLIST, abort its
job.  If the spool file is some process' output file, abort the job or
session it runs in.  This closes the spool file and either allows it to
print or allows you to delete it.

-Larry "MPE/iX Spoolers 'R' Us" Byler-