| Title: | Digital PostScript printers and their associated software |
| Moderator: | REGENT::LASKO HER |
| Created: | Wed Jan 24 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 7230 |
| Total number of notes: | 31971 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 7040.1 | one more job status starting 0 blocks transferred | STKHLM::HEGNELIUS | Fri Jan 24 1997 08:18 | 16 | |
One more customer experiencing the same problem.
VMS 6.2-H2, and DCPS 1.3 but this time it is a cluster.
The queues seems to work OK and suddenly one jobs stays in starting
status. The LPS console gets a connect message and then the message
0 blocks transferred, these messages goes on for ever until they
do STOP/ID on the symbiont holding the queue. This seems to work
under DCPS 1.3 but not on DCPS 1.2 where you have to reboot both the
LPS and the hanging node at the same time.
Any hints is appreciated.
Regards
Eva
| |||||
| 7040.2 | REGENT::WOLF | Mon Jan 27 1997 11:40 | 9 | ||
I had thought that we had dealt with this or a problem with a similar
symptom in V5.1. I believe it was related to either a network
glitch (the virtual circuit between the printer and the print
client being created and then disconnected prior to any
real work being performed) or relating to a job being aborted in its
infancy. At the moment I would be more inclined towards prospect
1 which you indicate some transient network anomaly.
jeff
| |||||
| 7040.3 | still starting | STKHLM::HEGNELIUS | Fri Jan 31 1997 09:53 | 7 | |
They both have v 5.1 so if their were any fixes their they
already have them. This happens all the time with different
printers and hosts.
Any hints?
Eva
| |||||