|
HP OpenVMS Systems Documentation |
|
HP TCP/IP Services for OpenVMS
|
| Previous | Contents | Index |
Each printer must have its own spool directory located under the SYS$SPECIFIC:[TCPIP$LPD] directory. The spool directory acts as a printer's spooling queue; it contains the files that are queued for printing on that particular printer. A printer spool directory should have the same name as the printer reference name and must be located on the machine to which the printer is attached. Specify the directory using a UNIX-style path name.
Each printer should specify a spool directory even if the printer is connected to another machine or is on another network. You specify a spooling directory in the printcap database using the sd symbol. For example:
:sd=/SYS$SPECIFIC/TCPIP$LPD/LOCAL1:\ |
The LPD records printer errors in a log file located in the SYS$SPECIFIC:[TCPIP$LPD] directory. You can set up a separate log file for each printer, or you can set up one to be shared by all local printers.
To specify the log file in the printcap database, use the symbol lf and specify the directory as a UNIX path. For example, to specify a log file for the print queue named LOCAL1, the printcap entry would be as follows:
:lf=/SYS$SPECIFIC/TCPIP$LPD/LOCAL1.LOG:\ |
To specify a log file that can be shared by all printers, specify the same file for each printer entry. For example:
:lp=LOCAL1:\ :lf=/SYS$SPECIFIC/TCPIP$LPD/TCPIP$LPD_LOGFILE.LOG:\ . . . :lp=LOCAL2"\ :lf=/SYS$SPECIFIC/TCPIP$LPD/TCPIP$LPD_LOGFILE.LOG: |
You can configure LPD to support remote printing on a system that does not implement the PrintServer extensions. You do this for individual queues by adding a ps field in the queue's printcap entry with a value of non_PS . The printcap entry looks as follows:
:rm=Remote1 :ps=non_PS Q |
If you do not define a ps entry, LPD assumes the printer supports the PrintServer extensions.
Note that you can also configure this option systemwide with the PS-extensions configuration option. Values for this option are non_PS and LPS . For more information about the LPD configuration options, see Table 24-1.
If a printcap entry does not have a
ps
field defined, LPD uses the value of the configuration option. By
default, LPD uses PrintServer extensions.
24.5 LPD Server Cluster Support
When you start LPD, the following print queues are automatically created:
LPD utility queues are outbound execution queues for printers on remote LPD hosts. The generic queue TCPIP$LPD_OUT can point to one or more outbound execution queues for each node in the OpenVMS Cluster, named TCPIP$LPD_OUT_nodename_nn, where nodename is the SCS node name of the cluster node, and nn is the number of the queue on that node.
By default, outbound execution queues are not created automatically when TCP/IP Services starts up.
The printcap attributes of the utility queues are defined by default as follows:
TCPIP$LPD_OUT_nodename_nn:\ :lf=/TCPIP$LPD_ROOT/000000/TCPIP$LPD_OUt_nodename_nn.LOG:\ :lp=TCPIP$LPD_OUT_nodename_nn:\ :rm=localhost:\ :sd=/TCPIP$LPD_ROOT/TCPIP$LPD_OUT_nodename_nn:\ |
Entries in the
printcap
file are required only if you want to change one of these default
settings.
24.5.2 Using Clusterwide Print Queues
Print jobs are queued to the TCPIP$LPD_OUT print queue. To specify the printer on the PRINT command line, include the following qualifiers.
For example, to print your LOGIN.COM file on the printer named XYZPRINT on the host LPDSVR.XYZ.ORG, enter the following command:
$ PRINT/QUEUE=TCPIP$LPD_OUT/PARAMETER=(HOST=LPDSVR.XYZ.ORG,PRINTER=XYZPRINT)- _$ SYS$LOGIN:LOGIN.COM |
You might want to associate DCL symbols with the destination printers, creating command names that are easy to remember. The new command names can be made available systemwide by including them in the system SYLOGIN.COM file.
The printer specified in the preceding example can be defined with the following command:
$ XYZPRINT :== $ PRINT/QUEUE=TCPIP$LPD_OUT - _$ /PARAMETER=(HOST=LPDSVR.XYZ.ORG,PRINTER=XYZPRINT) |
If the logical name is defined systemwide, the XYZPRINT command always
prints to the specified printer on the specified host.
24.5.3 Configuring a High-Availability LPD Server
You can use the LPD server cluster features to provide a
high-availability, load-balanced LPD server. To configure this, create
a cluster alias for all of the IP interfaces of your LPD server nodes.
On your LPD clients, specify the cluster alias as the LPD server to
which to send LPD jobs. For more information about load balancing and
the load broker, see Chapter 7.
24.6 Managing LPD Server Queues
To start the LPD server queues, enter the following command:
$ @SYS$STARTUP:TCPIP$LPD_STARTUP |
To stop the LPD server queues, enter the following command:
$ @SYS$STARTUP:TCPIP$LPD_SHUTDOWN |
To display the status of a remote queue, enter the LPQ command at the DCL prompt. To remove jobs from a remote printer queue, enter the LPRM command at the DCL prompt. For more information about these commands, refer to the HP TCP/IP Services for OpenVMS User's Guide.
The following example deletes all the jobs on remote print queue EIDER_DOWN_Q:
$ LPRM EIDER_DOWN_Q /ALL |
The TCPIP$LPD_ROOT logical name defines the LPD root directory, which is SYS$SPECIFIC:[TCPIP$LPD], by default.
You can redefine the LPD root directory by defining the TCPIP$LPD_ROOT logical name as follows:
$ DEFINE/SYSTEM/EXECUTIVE_MODE/TRANSLATION_ATTRIBUTES=(CONCEALED,TERMINAL) - _$ TCPIP$LPD_ROOT dev:[directory]) |
You do not have to change the printcap file when you define the LPD root directory. The root directory is defined in the printcap file using the following entry:
:sd= /TCPIP$LPD_ROOT/000000/MYQUEUE:\ |
You can grant or deny remote users access to the LPD server by entering the command SET SERVICE LPD /FLAGS=APPLICATION_PROXY. This causes LPD to authenticate remote users through the TCP/IP Services proxy database. You identify the remote users by adding communication proxy entries in the proxy database, TCPIP$PROXY.DAT. Each remote user allowed to access your local queues must have an entry.
To add a proxy entry, enter:
TCPIP> ADD PROXY user_name /HOST=host_name /REMOTE_USER=user_name |
For each host, define both its host name and alias name. If you need to use lowercase letters to specify a remote user name, enclose it in quotation marks. For example:
/REMOTE_USER="unixuser" |
You use wildcard characters when adding proxy entries for users on remote systems. For example, the following command allows any user on the remote host REMOTE1 to submit print jobs to the print queues on your system.
TCPIP> ADD PROXY R_USERS /HOST=REMOTE1 /REMOTE_USER="*" |
To disable authentication, use the /FLAG=NOAPPLICATION_PROXY option to the SET SERVICE LPD command. Use the /REJECT option to deny access from certain hosts. For example:
TCPIP> SET SERVICE LPD /REJECT=HOSTS=(loon,ibis,tern) |
The LPR/LPD spooler can notify you of selected events with OPCOM messages. To receive these notifications, enter:
$ TCPIP SET SERVICE LPD /LOG=option $ REPLY /ENABLE=OPCOM |
Some of the logging options are:
For a complete list of logging options, refer to the description of the
SET SERVICE command in the HP TCP/IP Services for OpenVMS Management Command Reference manual.
24.10 Using OpenVMS Flag Page Options
LPD supports all OpenVMS flag page print options, including:
To enable these features, use the VMS-Flagpages configuration option, as described in Table 24-1. This option applies to all print queues.
When you set the VMS-Flagpages option, LPD does the following:
Note that this configuration setting renders meaningless the
/PARAMETERS=NOFLAG qualifer to the DCL command PRINT.
24.11 Solving LPD Problems
In addition to the LPR and LPD symbionts, the LPD receiver logs diagnostic messages to the error log file specified in the printcap database (as described in Section 24.4.1.2).
Use the Symbiont-Debug and Receiver-Debug configuration options to control LPR/LPD diagnostic information recorded in the log files.
Symbiont-Debug and Receiver-Debug are bit-mapped values. The low-order three bits turn on all diagnostics generated by either the sender or the receiver.
To define these logical names, set the following bits in the value:
If you set the fourth bit, the LPD symbiont logs each buffer that it sends over the TCP/IP link, and the LPD receiver logs each buffer that it receives from the TCP/IP link. The log files let you see exactly what the LPD is sending (for outbound jobs) and receiving (for inbound jobs).
To set the fourth bit, enter:
Symbiont-Debug: 8 Receiver-Debug: 8 |
For example, to obtain all diagnostic information, set both options to 15.
Note that using these settings during normal system operation can affect the performance of LPD and may produce large log files.
For more information about the LPD configuration options, see Table 24-1.
The TELNET print symbiont (TELNETSYM) provides remote printing services that enable the use of standard OpenVMS printing features not available with the LPR/LPD print service. With TELNETSYM configured on your system, you can set up and manage a remote printer attached to a remote terminal server as if it were directly connected to your system. The TELNET symbiont functions like LATSYM, the symbiont for local area transport (LAT) software.
The TELNET symbiont performs the following functions:
This chapter reviews key TELNETSYM concepts and describes:
TELNETSYM is a true OpenVMS print symbiont; it performs all print
formatting functions, such as header and trailer page generation,
pagination, queuing, and handling of multiple forms. TELNETSYM extends
the OpenVMS print symbiont by redirecting its output to a network
(TELNET) channel.
25.1.1 TELNETSYM Process Names
TELNETSYM sets its process names to TCPIP$TNS1, TCPIP$TNS2, and so on.
Each TELNETSYM process can control up to 32 print queues. You can
control the maximum number of print queues by defining the
TCPIP$TELNETSYM_STREAMS logical, as described in Section 25.5.6.
25.1.2 TELNETSYM Modifications to the Output Stream
TELNETSYM adds escape (0xFF) bytes in the data stream so they are not mistakenly interpreted as TELNET protocol IAC commands.
TELNETSYM doubles any TELNET IAC characters found in the byte stream unless TCPIP$TELNETSYM_RAW_TCP is defined for the queue. The IAC character is a hexadecimal FF.
If the print job is queued with the /PASSALL qualifier, TELNETSYM sets up a binary TELNET channel by inserting IAC-DO-BINARY and IAC-WILL-BINARY escape sequences.
You can turn off this behavior by defining the logical name TCPIP$TELNETSYM_RAW_TCP for the queue. If you set this logical name, none of this processing is done.
The IAC-DO-BINARY sequence is 6 bytes, which are symbolically:
IAC, DO, BINARY, IAC, WILL, BINARY
The hexadecimal equivalents are:
FF,FD,00,FF,FB,00 |
TELNETSYM does not add any additional data to the stream other than that described. It does not insert form feed characters that were not present in the output from the OpenVMS print symbiont. Therefore, any additional characters observed as added to a print job come from the OpenVMS or other print symbiont (for example, HP PATHWORKS/Advanced Server for OpenVMS).
TELNETSYM can remove (suppress) any form feed (0x0c) characters that
the OpenVMS print symbiont adds to the beginning or end of print jobs.
Use the TCPIP$TELNETSYM_SUPPRESS_FORMFEEDS logical name to control this
function, as described in Section 25.6.4.1.
25.2 TELNETSYM Service Startup and Shutdown
The TELNETSYM service can be shut down and started independently of TCP/IP Services. This is useful when you change parameters or logical names that require the service to be restarted.
The following files are provided:
HP recommends that you place the DCL commands to start your TELNETSYM queues and define TELNETSYM logicals in the TCPIP$TELNETSYM_SYSTARTUP.COM command procedure. For more information about the commands to include, see the following sections:
To preserve site-specific parameter settings and commands, create the following files. These files are not overwritten when you reinstall TCP/IP Services:
Use the DCL command INITIALIZE/QUEUE to set up a TELNETSYM queue. Use the /PROCESSOR and /ON qualifiers as follows:
/PROCESSOR=TCPIP$TELNETSYM |
/ON="hostname:portnumber" |
For example, to set up a TELNETSYM queue named xyz_q to print using TELNETSYM to host printserver.xyz.com at TCP port 4242, enter:
$ INITIALIZE /QUEUE /PROCESSOR=TCPIP$TELNETSYM - _$ /ON="printserver.xyz.com:4242" xyz_q |
You can redirect the output of TELNETSYM to another queue rather than sending it directly to a remote printer. A queue with this setup is a relay queue. Use relay queues to funnel fully formatted output to an outbound LPD queue. LPD transfers jobs that are fully formatted on the sending side by OpenVMS.
In this case, TELNETSYM saves the output stream to a temporary file and then submits the file to the destination queue.
To set up a TELNETSYM relay queue, specify the /ON qualifier of the INITIALIZE/QUEUE command as follows, where qname is the name of the queue to which you want TELNETSYM to send its output.
/ON="TCPIP$QUEUE:qname" |
To set up a TELNETSYM relay queue named RELAYQ_4 to send output to the queue named LPD_Q4, enter:
$ INITIALIZE /QUEUE /ON="TCPIP$QUEUE:LPD_Q4" - _$ /PROCESS=TCPIP$TELNETSYM /DEVICE=PRINTER RELAYQ_4 |
You can manage and customize TELNETSYM for each print queue by defining logical names before you start the queue. Because the logical names are translated once at queue startup time, they can be defined differently for each TELNETSYM queue. Use the /SYSTEM qualifier when defining TELNETSYM logical names. You must stop and restart the print queue to establish the changes you make with logical names.
Some TELNETSYM configuration logical names are used to set a configuration option either ON or OFF. If the logical name is defined, the option is ON. If it is not defined, the option is OFF. Other logical names require a specific value.
The following sections describe TELNETSYM logical names.
| Previous | Next | Contents | Index |