To start your print queues, enter the following command

$ @SYS$MANAGER:TCPIP$LPD_STARTUP

To stop print queues, enter the following command:

$ @SYS$MANAGER: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. See DIGITAL TCP/IP Services for OpenVMS User's Guide for more information about these commands.

The following example deletes all the jobs on remote print queue EIDER_DOWN_Q:

$ LPRM EIDER_DOWN_Q /ALL

18.5 Controlling Access to Local Queues

You can grant or deny access to remote users by issuing the command SET SERVICE LPD /FLAGS=APPLICATION_PROXY. This causes LPD to authenticate remote users through the 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. Use uppercase and lowercase consistently.

You may use wildcards 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)

18.6 Receiving LPR/LPD OPCOM Messages

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

The logging options defined are:

• LOGIN --- LPD receiver startup and exit
• LOGOUT --- Job completion
• ACTIVATE --- Queue startup

LPD supports all OpenVMS FLAG PAGE print options, including:

• /FLAG qualifier of the DCL PRINT command
• /DEFAULT=FLAG setting on the LPD print queue
• /SEPARATE=FLAG setting on the LPD print queue

To turn on these features, define the system logical name TCPIP$LPD_VMS_FLAGPAGES. At queue startup time, enter:

$ DEFINE /SYSTEM TCPIP$LPD_VMS_FLAGPAGES

When you define TCPIP$LPD_VMS_FLAGPAGES, LPD does the following:

• Honors what OpenVMS instructs regarding flag pages for outbound jobs.
• Submits inbound jobs with /FLAG or /NOFLAG, based on the presence of the L card in the control file.
  Inbound jobs with an L card are submitted to the destination print queue as PRINT /FLAG.
  Inbound jobs without an L card are submitted to the destination print queue as PRINT /NOFLAG.
• Renders meaningless the DCL PRINT /PARAM=NOFLAG command.

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 in a manner that is similar to that of LATSYM for DIGITAL's local area transport (LAT) software.

The TELNET symbiont performs the following functions:

• Transfers record-oriented data to and from disks and printers.
• Configures printers attached to terminal servers that support TELNET.
• Supports outbound print jobs and offers preformatting to outbound print jobs.

This chapter reviews basic TELNETSYM concepts and describes how to set up and manage remote printers.

19.1 Reviewing Key Concepts

TELNETSYM transfers record-oriented data to and from disks and printers. Because 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.

19.1.1 TELNETSYM Modifications to the Output Stream

TELNETSYM modifies the print output stream as follows:

• 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.
• Because /PASSALL print jobs might contain 8-bit data, TELNETSYM sends the TELNET "do binary will binary" options-negotiation escape sequence before a print job that has been printed with /PASSALL.
  You can turn off this behavior by defining the logical name TCPIP$TELNETSYM_RAW_TCP for the queue. TELNETSYM does not send this sequence before printing a /PASSALL job.
  The "do binary will binary" sequence is 6 bytes, which are symbolically:
  IAC, DO, BINARY, IAC, WILL, BINARY
  In hexadecimal, this is:
  FF,FD,00,FF,FB,00
• TELNETSYM generates a form feed before the first job of a new print queue starts and at the end of every job. This is normal behavior for an OpenVMS print symbiont. To suppress this behavior, define TCPIP$TELNETSYM_SUPPRESS_FORMFEEDS for the queue.

TELNETSYM sets its process names to TCPIP$TNSYM1, TCPIP$TNSYM2, and so on.

19.2 Setting Up a Print Queue

Use the DCL command INITIALIZE/QUEUE to set up a TELNETSYM queue. Use the /PROCESSOR and /ON qualifiers as follows:

1. Specify the TELNETSYM image name in the /PROCESSOR qualifier:
   /PROCESSOR=TCPIP$TELNETSYM
2. Specify the host name and port number to which the queue sends the print data with the /ON qualifier:
   /ON="hostname:portnumber"

For example, to set up a TELNETSYM queue named xyz_q to print to host printserver.xyz.com at TCP port 4242, enter:

$ INITIALIZE /QUEUE /PROCESSOR=TCPIP$TELNETSYM - _$ /ON="printserver.xyz.com:4242" xyz_q

19.3 Setting Up Relay Queues

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.

TELNETSYM saves the output stream to a temporary file and then submits the file to the destination queue. TCP/IP is not used.

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

19.4 Managing and Customizing Your Print Queues

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. This places the logical name in the system logical name table and makes it available to all users.

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. Descriptions indicate when a value is required.

19.4.1 Controlling Stream of Print Bytes Sent Over the Link

If a remote printer does not support the TELNET protocol, you can still print to such a printer by suppressing all TELNET modifications of the output stream with the following logical names:

• TCPIP$TELNETSYM_RAW_TCP
  Suppresses all TELNET type modifications of the print output stream. This is for cases where the remote printer/terminal server does not implement the TELNET protocol and, instead, expects the raw data stream.
  This logical name also stops TELNETSYM from doubling IAC characters and sending the TELNET escape sequence to negotiate binary options for files printed /PASSALL.
• TCPIP$TELNETSYM_SUPPRESS_FORMFEEDS
  Suppresses form feeds between jobs. This includes the form feed that is normally sent before the first job printed to a print queue and the form feed sent at the end of every job.

By default, TELNETSYM sends messages to the operator and records error and informational messages in the file TCPIP$TELNETSYM.LOG. This file is located in SYS$SPECIFIC:[TCPIP_LPD]. Logical names are available to modify the way the TELNETSYM logs information and the type of information it reports. For example, TELNETSYM can log diagnostic messages that you can use when troubleshooting problems with a link.

Use the following logical names to modify error logging:

• TCPIP$TELNETSYM_VERBOSE
  Turns on the logging of TELNETSYM diagnostics to the file TCPIP$TELNETSYM.LOG. These diagnostics include informational messages that indicate when links have come up or gone down and error messages.
• TCPIP$TELNETSYM_NO_OPCOM
  Stops TELNETSYM from sending messages to the operator console.
• TCPIP$TELNETSYM_DEBUG
  Used with TCPIP$TELNETSYM_VERBOSE, this logical name tells TELNETSYM which diagnostic message types to log.
  Specify a value for each bit. Each bit set in the value turns on a particular logging function. The options are:

  Bit 0	Tracks the flow of code, for example: xyz-n-xyz-routine entered
  Bit 1	Tracks the allocation of memory, for example: just freed address 7F0000
  Bit 2	Logs the bytes sent and received over TCP/IP link.

  
  To set a bit, assign the value to the logical name whose binary equivalent would have the bit set. For example, you can tell TELNETSYM to log everything that it writes to, and receives from, the TCP/IP link by entering:

  $ DEFINE /SYSTEM TCPIP$TELNETSYM_DEBUG 4

  
  Decimal 4 is binary 100 with bit 2 set. Note that you can achieve different combinations by setting more than one bit in the value. A value of 3, for example, sets bits 0 and 1, and, therefore, causes logging of flow of code and memory allocation diagnostics.
  If TCPIP$TELNETSYM_DEBUG is undefined, TELNETSYM does not log these diagnostics.
  Bit 2 is useful in unassisted problem solving. Bits 0 and 1 are primarily for Compaq use. However, with knowledge of PSM$ symbionts, you might find all the options useful.

• TCPIP$TELNETSYM_LOG_KEEP
  By default, TELNETSYSM saves all log files. Define this logical name to limit the number of log files saved. The value assigned to this logical name is the number of versions of a log file TELNETSYM will allow before it starts purging. When the number of files reaches the number you specified, TELNETSYM starts purging files.
  For example, to configure the queue to purge after more than three copies of the same log file are created, define the logical name as follows:

  $ DEFINE /SYSTEM TCPIP$TELNETSYM_LOG_KEEP 3

• TCPIP$TELNETSYM_SCRATCH
  By default, TELNETSYM stores log files and any temporary files created by relay queues in the directory SYS$SPECIFIC:[TCPIP_LPD]. You may change the default directory for one or all of your TELNETSYM queues. For example:

  $ DEFINE TCPIP$TELNETSYSM_SCRATCH device:[directory.path]

TELNETSYM configuration logical names in this category correspond directly to item list options for the $QIO SETMODE function. Enter TCPIP SHOW PROTOCOL TCP /PARAMETER to see the default values for these SETMODE options.

• TCPIP$TELNETSYM_DROPTIME
  If defined, this logical name uses the value set with the $QIO SETMODE option TCPIP$C_TCP_DROP_IDLE.
  Note that the value for drop time must be greater than the value for probe time. When you define only one of these TELNETSYM logical names, the default value will be used for the other logical name.
• TCPIP$TELNETSYM_KEEPALIVE
  Turns on the the $QIO SETMODE TCPIP$C_KEEPALIVE option.
• TCPIP$TELNETSYM_PROBETIME
  If defined, this logical name uses the value set with the $QIO SETMODE option TCPIP$C_TCP_PROBE_IDLE.
• TCPIP$TELNETSYM_SNDBUF
  If defined, this logical name uses the value set with the $QIO SETMODE option TCPIP$C_SO_SNDBUF.

If a network link is unavailable, the TELNET symbiont attempts to open one. Printing starts when the link is successfully established. The TELNET symbiont continues to try to establish a network link until it is successful or until a retry interval you define has expired.

The logical name TCPIP$TELNETSYM_RETRY_INTERVAL defines the time for TELNETSYM to wait between link-establishment retries when link establishment has failed. The value for this logical name is an OpenVMS delta time.

If this logical name is not defined, TELNETSYM defaults to a wait period of 3 minutes between retries.

For example, to define a retry interval of 30 seconds, enter:

$ DEFINE /SYSTEM TCPIP$TELNETSYM_RETRY_INTERVAL "0 00:00:30.00"

19.4.5 Releasing a TELNETSYM Link

By default, TELNETSYM releases an open link at the end of a print job. This behavior is useful when multiple systems contend for the same printer. Configuring TELNETSYM to release the link at the end of a job allows other systems to print quickly. However, this behavior can be a disadvantage because of the overhead involved with link creation for each print job.

When there is little or no contention for a printer, it is useful to configure TELNETSYM to release the link only after a certain period of idle time has passed. With this approach, TELNETSYM waits for the configured idle time to elapse and then closes the link. This option works well within batch printing applications.

Use the logical name TCPIP$TELNETSYM_IDLE_TIMEOUT to define the length of time to wait before terminating an inactive link. Specify a value that is an OpenVMS delta time.

For example, to define a link-idle-timeout of 10 minutes, enter:

$ DEFINE /SYSTEM TCPIP$TELNETSYM_IDLE_TIMEOUT "0 00:10:00.00"

19.4.6 Setting the Number of Execution Queues

The logical name TCPIP$TELNETSYM_STREAMS defines the number of execution queues handled by each TELNETSYM process. The value you enter (a number from 1 through 16) when defining this logical name is passed to the PSM$PRINT system routine. The default is a maximum of 16 queues per symbiont process.

An important use of this logical is to turn TELNETSYM into a single-threaded symbiont (value=1) where each queue runs its own process. This makes diagnosing problems easier and lessens the consequences of a crash.

If you are defining this logical name, define it once. Do not define it differently for each TELNETSYM print queue.