Re: Spool File to Remote Outq "Stuck"

John

This seems to be a 'feature' of remote printing.  We get this from
time-to-time, more often on large prints.

My usual activities are

1.  End the remote writer with an *IMMED
2.  Tell the remote user to turn off printer, count to 5, turn back on.
Wait until their printer is ready
3.  Start the remote writer

After 15-30 seconds, things usually start chugging through.




                    "John P. Walsh"
                    <john_walsh@icdc.co        To:     <midrange-l@midrange.com>
                    m>                         cc:     "Sgt. John Walsh"
                    Sent by:                   <jwalsh@haverfordpolice.org>
                    midrange-l-admin@mi        Subject:     Spool File to 
Remote Outq "Stuck"
                    drange.com


                    12/09/02 12:36
                    Please respond to
                    midrange-l





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

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.