Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!decwrl!ucbvax!info-vax
From: zar%Xhmeia@CIT-HAMLET.ARPA
Newsgroups: mod.computers.vax
Subject: VMS Printer question
Message-ID: <8511261405.AA18714@ucbvax.berkeley.edu>
Date: Mon, 25-Nov-85 18:12:03 EST
Article-I.D.: ucbvax.8511261405.AA18714
Posted: Mon Nov 25 18:12:03 1985
Date-Received: Wed, 27-Nov-85 00:27:02 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 19
Approved: info-vax@sri-kl.arpa

Under VMS V4, when a print job is aborted, the system tries to write
a one/two line message to the printer which explains the current print
session was aborted. This is a problem when you want to requeue a print
job to another device while one is being serviced. If the printer doesn't
accept I/O, the job can never be removed from the print queue because the
system insists on writing this ***SILLY*** message (and wasting a page
of paper to boot). Not only that, but the printer queue can NEVER be
stoped/deleted until the job disappears! The work-arounds are messy! To
stop the job one can do either of the following:
	1) Write your own print symbiont that does thinks better (yech).
	2) STOP/QUEUE/NEXT printer, then STOP/ID=pid_of_printer_symbiont
	   (also yech).
Now for my questions: Does anyone have #1 working? Does DEC plan to
change this?

						From The Great
						     Zar
						CIT Chemistry
						ZAR%XHMEIA@HAMLET