BARR/PRINT for TCP/IP, in combination with BARR/SPOOL or a Barr RJE product, is a PC-based solution for printing from a UNIX host over a TCP/IP network with the 4.3 Berkeley Software Development (BSD) Line Printer Daemon (LPD) protocol. FTP Softwares PC/TCP software provides the TCP/IP interface.
The Barr PC appears as a remote BSD printer to the UNIX host. Your host documentation contains information about how to print to a remote BSD printer.
In the sample configuration in Figure 1-1, a PC running BARR/PRINT for TCP/IP acts as a remote LPD. The UNIX host uses a Line Printer Request (LPR) utility to print on printers attached to the remote LPD.
Figure 1-1. With BARR/PRINT for TCP/IP, your UNIX host can print to printers connected to the Barr PC.
BARR/PRINT for TCP/IP supports printing from UNIX hosts. Special features include print spooling, printing on multiple printers, and sharing a single printer between several host print queues.
Print Speed You can use BARR/PRINT for TCP/IP with a variety of printers. Print speeds on single and multiple printers range from 30 characters per second (cps) to more than 20,000 lines per minute (lpm).
Multiple Printers BARR/PRINT for TCP/IP appears as a remote LPD and thus allows up to four TCP/IP connections to hosts on the network. It supports parallel, serial, and channel-attached printers. Parallel ports are named LPT1, LPT2, and LPT3 and serial ports are named COM1, COM2, COM3, and COM4. The Barr PRINT370 option connects channel-attached printers. You can also assign printer streams to disk and screen.
Spool Support BARR/PRINT for TCP/IP allows you to spool print files received from the UNIX host. By spooling files, you can increase printer efficiency.
Print Simultaneously from IBM and UNIX Hosts BARR/PRINT for TCP/IP combined with Barr RJE enables you to share high-speed printers between your mainframe and UNIX-based computers. You can simultaneously print from IBM hosts, UNIX hosts, and local area network-based (LAN-based) PCs to parallel and serial printers.
Native TCP/IP BARR/PRINT for TCP/IP supports using native TCP/IP (a standard BSD socket) where the host opens a socket (port 9100 by default) to pass through data.
Optional S/370 Channel-Attached Printer Support Barrs PRINT370 option drives System/370 (S/370) channel-attached printers at their maximum speeds. If you install an S/370 channel emulator adapter in the PC with BARR/PRINT for TCP/IP, you can attach up to six S/370 channel-attached printers to the adapter with bus and tag cables.
Optional Dataproducts Printer Interface Support The Dataproducts Printer Interface (DPI), developed by the Dataproducts Corporation, drives high-speed printers and typesetting equipment. Barr offers BARR/DPI and BARR/DPI2 adapters to attach a PC to a printer with a DPI and support for carriage control commands.
Because BARR/DPI appears as a parallel printer adapter (LPT1, LPT2, LPT3) to the PC, all software used with these ports will function with BARR/DPI. It is completely compatible with Basic Input/Output System (BIOS) and Disk Operating System (DOS).
Barrs TCP/IP printing services are based on Request for Comments (RFC) 1179, which contains the communication specification for LPD printing. Table 1-1 below lists supported RFC1179 features.
Table 1-1. Supported RFC1179 Features
|
Feature |
Description |
|
5.1 01 Print any waiting jobs |
Starts the printing process if it is not already running. |
|
5.2 02 Receive a printer job |
Controlled by a second level of commands. LPD gets commands by sending them over the same connection. |
|
6.2 02 Receive control file |
Control file is ASCII stream. Ends of lines are ASCII LF. Total number of bytes sent as first operand. Name of control file sent as second. It should start with ASCII cfA followed by 3-digit job number followed by host name that constructed the control file. |
|
6.3 03 Receive data file |
First operand is total number of bytes in the stream or zero. Name of file should start with ASCII dfA (might change to dfB, dfC, etc.) followed by 3-digit job number followed by host name that constructed the file. In the Barr product, LPR does not send a zero byte count and LPD will not support a zero byte count. |
|
6.4 04 Receive control file first |
Allows you to send a control file followed by multiple data files when you receive files to the print spool, which means you can print multiple copies of a file. |
|
6.5 05 Receive data file with unspecified length |
Allows the host to send a data file without specifying the length. The host must send the control file first because the end of file is acknowledged when the host closes the connection. |
|
6.6 Receive job subcommand ordering |
Allows you to send multiple jobs in one session to the same queue; however, multiple jobs (if different) will not be printed. Only the first data file will be printed while the other jobs merely increment the copy count in the spool header. |
|
6.7 Interoperability between old and new clients and servers |
New servers understand both old and new commands and old servers only understand old commands. New clients should try to use the new Receive Control File First command (6.4 04). If that fails, new clients should try the old commands. |
|
7.1 C Class for banner page |
Sets the class name to print on the banner page. If name is omitted, name of host on which file is printed will be used. Class operand is used to display the host from which the printing job originated. |
|
7.2 H Host name |
Specifies the name of the host to be treated as the source of the print job. Command must be included in the control file. |
|
7.4 J Job name for banner page |
Sets the job name to print on the banner page. It can be omitted. Conventionally used to display the name of the file or files printed. Ignored unless the print banner command code L is also used. |
|
7.5 L Print banner page |
Causes banner page to print. User name can be omitted. Class for banner page (C) and job name for banner page (J) must precede this command in the control file to be effective. |
|
7.7 N Name of source file |
Specifies the name of the file from which the data file was constructed. |
|
7.8 P User identification |
Specifies the user identification of the entity requesting the printing job. Must be included in the control file. |
|
7.11 U Unlink data file |
Indicates that the specified file is no longer needed. Only use for data files. |
|
7.19 f Print formatted file |
Causes data file to be printed as plain text file with page breaks. Discards all ASCII characters except HT, CR, FF, LF, and BS. |
|
7.22 l Print file leaving control characters |
Causes specified data file to be printed without filtering the control characters (which the f command code does). |
You can install BARR/PRINT for TCP/IP on a PC that meets the following requirements:
ISA or EISA bus (if you purchased the Barr ETHERNET2)
PCI bus (if you purchased the ETHERNET PCI adapter)
One 16-bit or 32-bit slot (if you purchased the Barr ETHERNET2 or ETHERNET PCI adapter)
A PC with at least 640 kilobytes of memory
DOS 5.0 or later version
Barr RJE hardware and software or BARR/SPOOL software
PC/TCP for DOS software from FTP Software, Inc.
The BARR/PRINT for TCP/IP package contains the BARR/PRINT for TCP/IP software and an ETHERNET2 (ISA) adapter or ETHERNET PCI adapter, depending on what you ordered.
BARR/PRINT for TCP/IP software disk
ETHERNET2 adapter
3Com EtherLink III User Guide
3Com EtherDisk
Ethernet PCI Adapter
Intel EtherExpress PRO/100 TX PCI LAN Adapter Installation Guide
Intel EtherExpress Disk