7 Laser Revisions #2                             Oct 1990   J    With the introduction of the FILE symbiont transfer mechanism, we foundH that we sometimes wanted to print documents on a remote laser printer. IG have added support for the PARAMETER parameter on the laser command, so F that queue rerouting is possible on the remote node. All control codesG for the laser setup are done on the local node and imbedded in the file  to be printed.  H    In the example supplied, (see LASER.PAR) all laser printers are validJ from SYS$PRINT. It is assumed that the user will use the /PARAMETER optionH to specify a remote queue to print on (not on the local node). With thisG setup, there is no check to validate that the remote queue can actually L print with laser settings. In this example, the local node owns no printers,K the symbiont controlling SYS$PRINT is a FILE symbiont, and the listings are K rerouted to a remote node. I have setup in LASER.PAR, that 3 laser printers L are valid from SYS$PRINT, with the various fonts for each. (Also the defaultK queue is SYS$PRINT if not supplied). When the user wants to laser something # on a remote node, they would enter:   8          LASER/FONT=COUR10PP/PARAMETER=LASER my_file.lis  F The queue LASER does not exist on the local node, the listing file is K build using the appropriate setup modules in SYSDEVCTL.TLB (in sys$library) L from the SYS$PRINT queue. The listing file is transferred across the network/ and rerouted to queue LASER on the remote node.   ,                                 R. Armstrong