| Title: | DEC TCP/IP Services for OpenVMS |
| Notice: | Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System |
| Moderator: | ucxaxp.ucx.lkg.dec.com::TIBBERT |
| Created: | Thu Nov 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5568 |
| Total number of notes: | 21492 |
I have a customer who's having problems with lpd, ucx v3.3 eco 4.
When he sends printing a big job (140.000blocks) it's not printed and
nothing is at the log file.
The sequence is:
-Copies the file to the spool directory, in this moment if we see
the status of the queue it's processing, when the copy is finished
the queue becomes in holding state and the sequence starts again, the
file is copied again to the spool directory and the file never becomes
printed.
Smaller jobs are well printed, what's happening?
Any ideas?
Thanks is advanced
Amalia Mart�n
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5519.1 | TCP idle timeout expiration | GIDDAY::TAN | Mon May 19 1997 00:16 | 16 | |
Sounds suspiciously like the problem where UCX established a TCP connection to the remote LPD server, then started reading the print file, but by the time it has finished processing the job, the TCP connection has timed out! If this is the case, then there are 2 solutions: a) set the idle timeout on the LPD server (eg, HP Jetdirect card) to some larger value, say 90 seconds, this would give the UCX/LPD client a fighting chance of finishing processing the job; b) the order of things has changed in the later UCX, with ECO, now the TCP connection is only established after the job has been processed, so no danger of timing out the TCP link. /David | |||||