TCP/IP, LPR, LPD Printing

TCP/IP, LPR, LPD Printing:  Overview

Most of the printing today occurs over TCP/IP networks.  It often uses the LPR and LPD protocols.

TCP/IP, LPR, LPD Printing:  Challenges  

The needs associated with TCP/IP, LPR, and LPD printing usually revolve around connectivity with hosts and printers.

TCP/IP, LPR, LPD Printing:  Barr Systems' Solution

Our Barr Enterprise Print Server platform fully supports TCP/IP and LPR / LPD for printing.  The BARR/PRINT TCP/IP input module allows you to receive data from any TCP/IP-based host (mainframes, UNIX computers, AS/400s, and so on) with LPD/LPR or with direct socket connections. The LPD queue name, job name, and user name, can be used as criteria to route the job to any final destination using our Document Distribution and Delivery capabilities.

On the output side, the software supports sending print to unlimited LPR printers.

Read More

The Barr Enterprise Print Server with BARR/PRINT TCP/IP appears as a remote 4.3 BSD printer to the UNIX host. It implements the LPD to service LPRs from BSD 4.3 and System V hosts, or any type of system that provides LPR emulation. BARR/PRINT TCP/IP also provides a direct socket connection, which might be more appropriate depending on your needs.

Key features:

• Receives files from multiple hosts such as IBM® mainframes, UNIX® machines, AS/400®s, and Windows® Servers and clients
• Supports unspecified file lengths
• Receives data in ASCII (PCL and PostScript), Barr S/370 channel, binary, or VBM (for Xerox Metacode)
• Supports file transfers across a TCP/IP socket
• Automatically routes a single job to multiple locations without duplication
• Supports an unlimited number of LPD queues and the maximum number of socket ports allowed on the computer
• Receives data from any TCP/IP-based host, including mainframes equipped with packages such as IBM’s IP Printway and Levi Ray and Shoup®'s VPS/LCDS
• Supports line print queue (LPQ) and line print remove (LPRM)
• Uses RFC variables in the TCP/IP control file, including LPD queue name, job name, and user name, as criteria to route the job to any final destination
• Handles multiple data files with one control file
• Supports multiple control files in a single transmission
• Handles and preserves all control file information
• Customizes banner with control file information
• Supports RFC1179