zar%Xhmeia@CIT-HAMLET.ARPA (11/26/85)
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
TIHOR@NYU-CMCL1.ARPA (Stephen Tihor) (11/26/85)
STOP/QUEUE/RESET \\ Stephen Tihor / CIMS / NYU / 251 Mercer Street / New York, NY 10012 // (( DEC Enet: RHEA::DECWRL::"""TIHOR@NYU-CMCL1.ARPA""" NYUnet: TIHOR.CMCL1 )) // ARPAnet: Tihor@NYU-CMCL1 UUCPnet address: ...!ihnp4!cmcl2!cmcl1!tihor \\ -------
rick@NGP.UTEXAS.EDU (Rick Watson) (11/27/85)
Have you tried STOP/QUEUE/ABORT? I have found this to be useful when I am about to do a DELETE/QUEUE. Rick Watson University of Texas Computation Center arpa: rick@ngp.UTEXAS.EDU rick@ngp.ARPA uucp: ...seismo!ut-sally!ut-ngp!rick rick@ut-ngp.UUCP bitnet: ccaw001@utadnx phone: 512/471-3241