HP OpenVMS Systemsask the wizard |
The Question is: Our site has 5 Alphas and 4 network attached printers (JetDirect). I cannot find any discussion that recommends a model such that all Alphas have access to all printers. 1) One Alpha that has the "master" queues feeding the printers, and the other Alphas feeding this "master" Alpha (i.e. PRINTJOB -> ALPHA1 -> ALPHA2 -> JETDIRECT)? 2) All Alphas feeding the JetDirect simultaneously via UCX$TELNETSYM (i.e. PRINTJOB1 -> ALPHA1 -> JETDIRECT <- ALPHA2 <- PRINTJOB2)? If option 1 is the recommendation, how can a VMS print queue feed another VMS print queue on a different machine? My concern with option 2 is print job collision as well as JetDirect "stress attack". Many thanks. The Answer is : OpenVMS Engineering has no particular recommendations on third-party IP-based printers. Third-party Postscript printer information is covered in the DCPS (DECprint) software product description (SPD). There are many previous discussions of dealing with third-party IP printers, particularly including topic 1020. TCP/IP Services supports distributed printing to a target printer, assuming the printer supports it. Route-through printing can be configured by setting up LPD on the OpenVMS host. Various LPD discussions exist, including topic 2507. TCP/IP Services V5.0A or later is recommended.
|