[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::postscript_printing

Title:	Digital PostScript printers and their associated software

Moderator:	REGENT::LASKOHER

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

7149.0. "DCPS v1.3 and STALLED queues" by 48276::MATHIEU () Wed Apr 09 1997 05:42

    Hello,
    
    My Customer use DCPS 1.3 . When the printer becomes STALLED because
    paper of jam or other paper problem , if this problem stays some
    minutes , the printer stays always STALLED. The customer must Stop and
    start queue.
    
    Why the queue stays STALLED when the printer is ready ? IS there a
    timeout or other reason ?
    
    I use VMS 5.5-2 , Lat Printer (with Decserver) and DCPS 1.3 .
    
    Thanks for help
    
    Philippe

T.R	Title	User	Date	Lines
7149.1		REGENT::POWERS	`Wed Apr 09 1997 12:03`	5
	What printer(s)? Presumably they are connected via serial line from DECserver to printer? Is the return channel from the printer to DECserver operable? - tom]
7149.2		48276::MATHIEU	`Wed Apr 09 1997 12:25`	9
	Hi, My question is for a digital declaser 2100. Sometimes after a STALLED, if the Stalled stays longtime , it's not possible to print . The customer must Stop, Start and sometimes switch off printer. The printer is behind serial line on a decserver. Philippe
7149.3		REGENT::POWERS	`Thu Apr 10 1997 12:13`	32
	Depending on how the data flow through the DECserver is managed, I could suspect that there is a deadlock in either the printer, the DECserver, or the host based on bad flow control. If the printer, for example, repeatedly sends "jammed" messages (and I don't think it does), then these messages can get queued up in the DECserver because the host has flow controlled the line because it's still dealing with the first message. The DECserver can back up and flow control the printer, which then backs up and can't accept any new data because it's still trying to report on its last message. Even when the problem is fixed, the accumulated data is clogging the lines and flow control is out of synch. That what STALLED really is, a notification of flow control not having been cleared fast enough. HP printers and some of those that emulate them (again, NOT the 2100 as far as I know) send flow control when a jam occurs. This makes it difficult to interrogate the printer about the cause of a jam or error, and can instigate these deadlocks. Okay, I've just explained to you why the 2100 isn't as bad as these other printers are, but your problem is with a 2100. So is there a fix? I don't know. I do know that stopping and restarting the queue or power cycling the printer do normally cause loss of the job state, requiring reprinting from the beginning, so those fixes do have costs. How about a mechanical tuneup on the printer to minimize the likelihood of jams? That might minimize the occurrence of the problem. Sorry I can't be more assertive in suggesting a fix.... - tom]