Technical data

If users access a setup module frequently, you can associate the setup module
with a queue, so that all print jobs submitted to that queue are printed with
the setup module automatically. See Chapter 8 for instructions.
7.6 Persistently Loading PostScript Resources
Note
This feature applies only to desktop printers; PrintServer printers are
loaded with persistent resources using the PrintServer software.
Downloading PostScript code with every print job can adversely affect printing
performance. To resolve this problem, you can load a module that permanently
resides in the printer.
The module LPS$PERSISTENT_RESOURCES loads persistently to desktop
printers. To create a persistent PostScript module, follow these steps:
1. Create a new device control library for site-specific PostScript setup
modules, using the following command:
$ LIBRARY/CREATE/TEXT SYS$COMMON:[SYSLIB]library-name.TLB
2. Edit the SYS$STARTUP:DCPS$STARTUP.COM file to include the new
device control library in the search list. Use the following command in the
DCPS startup file:
$ DEFINE/SYSTEM/EXECUTIVE/NOLOG DCPS_LIB DCPS$DEVCTL, "library-name/DATA=POST"
3. In the execution queue definition for each PostScript printer to which you
want to load the setup module, ensure that the logical name DCPS_LIB is
entered in parameter 3 as the device control search list logical name.
4. Save the DCPS$STARTUP.COM file.
5. Stop the queues for the printers affected by the change, using the
STOP/QUEUE/RESET command for each queue.
6. Execute the new DCPS$STARTUP.COM file.
7. Test each print queue by sending two print jobs to the printer. The setup
module is loaded with the first print job sent to the printer. The setting
should be effective for the second print job, as well.
7–8 Creating Setup Modules and Device Control Libraries