|
WSupported on Windows
|
USupported on Unix
|
VSupported on OpenVMS
|
|
System option #22 determines how the LPQUE statement interfaces with the operating system.
If you set option #22 on Windows, the runtime sends LPQUE arguments to the file DBLDIR:dblpq.bat, which can contain customized print commands. If you don’t set this option, the runtime first checks to see if the PRINT_METHOD environment variable is set and, if not, sends the print job directly to the Windows Print Manager. Option #22 can be set in the environment or the synergy.ini file. See LPQUE. If you want more functionality than the default LPQUE statement provides, we recommend that you not set option #22 and that you use the Synergy Windows printing API instead. (See Synergy Windows Printing API for more information.)
If you set option #22 on Unix, the runtime sends LPQUE arguments to the script file DBLDIR:dblpq, which you can change to your own printing specifications. The LPQUE statement then executes the arguments in dblpq instead of those in the default printing program. If you don’t set this option, the LPQUE statement executes the default printing program, which is either lp (the System V implementation) or lpr (the BSD implementation).
We recommend that you examine the dblpq file to make sure it’s set up appropriately when you install Synergy DBL.
If you set option #22 on OpenVMS and the program is running from an interactive session, the LPQUE statement spawns a PRINT statement to print a specified file, which enables you to add PRINT options after the filename. If you don’t set this option, or if you do set it and the program is not running from an interactive session, the LPQUE statement uses the $sndjbc system service to print a specified file. Any switches that follow the filename are ignored. This feature works within detached or batch processes. You cannot use wildcard characters in the file specification.
