Spool File to Remote Outq "Stuck"

I have an app that generates a spool file that is routed to a remote
location.  There are a number of files waiting to print but are not doing
so.

There are a total of five similarly configured remote locations.  Four of
the five are receiving their files.  My 400 is attached to my lan.  On the
lan there are modem/routers that are configured to maintain a connection
(via dialup) to a similar device at th the remote location.  At the other
end there is a print server and printer.

The outq is up and running indicating a status of RLS similar to the other
four working ones.  The first spool file shows a status of SND; the
following files show a status of RDY.  I can ping and telnet into the
modem/routers.  I can also ping and access the print server remotely to do
diagnostics and successfully send a test page to the printer.

It seems there is sometype of problem with the first spool file.  I can't
change it nor can I delete it.  The only action I can do on it is to hold it
and then release it at which point it returns to a SND status.

Is there a way to get rid of this file.  I am hoping that if i did so the
other files would then print.  The only thing I can think of at this point
is to endtcp and re-start it.

John Walsh
jwalsh@haverfordpolice.org