info-vax@ucbvax.ARPA (08/13/85)
From: Lars_Palmer_H{ssle%QZCOM.MAILNET@MIT-MULTICS.ARPA I have a VMS question that I must ask the world under VMs we ran a large numeber of printers without trouble. The system was configurted in such a way that 1)the printer ques had "logical" names eg start/que lp_adb ttta5: 2)there was a logical name eg assign/system lla5: lp_adb the effect was that it was possible to both print and write to lp_adb from a program that did not communicate withthe spooler eg: PRINT file LP_ADB COPY file LP_ADB both worked. This does not seem possible to achieve in a VMS4 enviroment exept by starting the que as start/que TTA5 on H0::TTA5: this leads to 2 bad problems 1)if there is a device problem it is not possible to move the printe to another interface port as the queue has the hardware name (and is so known by various pieces of software) and 2)it is difficult in a cluste to keep the que names unique if they are tied to hardware names anyone have the same problem and any that has solved it ? ------------------ a second related problem under VMS 3 it was possible to set the formsize of the terminal as a set terminal/permanent. this formsize was then respected wenever anything was printed on the printer under VMS 4 things that are passed to printers without the /FORM= are printed on foeRM=DEFAULT that has has to be the same throughtout the cluster WE WANT TO HAVE DIFFERENT SIZE PAPER IN THE DIFFERENT PRINTERS for default printing any one that can give me any help thanks lars Palmer