gdmr%cstvax.edinburgh.ac.uk@CS.UCL.AC.UK (George D M Ross) (03/11/86)
From Eric Gisin, egisin@waterloo.csnet: >It currently stops the job controller, which says it received an EOF. >..... (the job controller and symbiont seem to use a mailbox >assigned to sys$input and sys$output to communicate). Ah. That would explain why the job controller shut down when my modified symbiont died, having claimed it (the job controller) had received a number of dud requests and an EOF. Presumably the symbiont's traceback information would go to SYS$OUTPUT. Anyway, while we're on the subject of print symbionts, does anyone know of a clean way of a user-output routine detecting the end of a print job, or alternatively detecting when its queue has drained? The scenario is that we have a Gandalf PACX 2000 interposed between the printers and the various hosts which might want to talk to them. The symbionts and output filters in the various hosts toggle DTR and are connected to the printer by means of a programmed call. At present they decide when to relinquish the printer on the basis of a timeout. It works very nicely, but it's rather inelegant.... George D M Ross, Dept. of Computer Science, Univ. of Edinburgh, Scotland Phone: +44 31-667 1081 x2730 JANET: gdmr@UK.AC.ed.cstvax --> ARPA: gdmr@cstvax.ed.AC.UK UUCP: <UK>!ukc!cstvax!gdmr
janderson@hqafsc-vax.UUCP.UUCP (02/12/87)
I remember reading or hearing at one time that print symbionts in
Version 4.X VMS can service more than one queue at a time. By
default, each queue started up has its own symbiont hanging around
in memory. I've been told that the user community here has ordered
over 20 printers to be distributed around. This could get serious.
Does anyone know anything about this?
------