Follow the instructions in your BARR/SPOOL or Barr RJE product manual to load and configure the Barr base software. Then see this chapter for additional BARR/PRINT for TCP/IP software settings.
The Barr software allows you to choose how to process and print files. You can convert files you receive from an ASCII source (such as a UNIX host) to an S/370 channel format and print the files on an S/370 channel printer. You can also preserve control file information from the UNIX host. For example, if your host sends a files UNIX file name, host name, user name, class name, or job name, you can retrieve them with the file. The software stores this information as file attributes.
You must set file attributes for Barr file processing. These attributes describe each file to the Barr software and tell how to print the file. File attributes display on the Print Spool screen. See the Print Spool Operation chapter in your BARR/RJE manual or your BARR/SPOOL manual for more information about how you can use file attributes to select files to print.
You can use the following software options to set attributes for files received from BARR/PRINT for TCP/IP devices:
You can extract the values of Jobname and Formname from the LPD control file with an option on the TCP/IP Queue Options screen. If you set Process LPD control file to Yes, the Barr software generates a banner with control file information.
Most UNIX hosts do not send a job name unless you request a banner page for the job.
You can extract file attributes from data in the file with the Process LPD control file options on the TCP/IP Queue Options screen and the OUTPUT statement or Spool header from data options on the Assign Devices screen.
You can set the class file attribute for the device from which you receive the file with the Class option on the Assign Devices screen. You can assign a separate class for each TCP/IP device. By default, the software assigns files received from the first TCP/IP device (BARRTCP1) a class of 1, files from the second TCP/IP device (BARRTCP2) a class of 2, and so forth.
If you use more than one method to set file attributes, you might overwrite some file attributes. The Barr software first updates the spool header with information extracted from the file by the OUTPUT statement or Spool header from data options. Then the software updates the spool header with LPD control file information. If you select both the OUTPUT statement and Process LPD control file options, the file attribute information taken from the control file overlays the file attributes specified in the OUTPUT statement.
This chapter discusses each BARR/PRINT for TCP/IP parameter available on sample Barr RJE screens. Screens might differ slightly for BARR/SPOOL.
To reach the screens for BARR/PRINT for TCP/IP, start at the Installation Description menu.
Select BARR/PRINT for TCP/IP Description.
The BARR/PRINT for TCP/IP Queues screen displays.
You can configure each BARR/PRINT for TCP/IP queue separately by selecting the first available queue (for example, BARRTCP1) on the BARR/PRINT for TCP/IP Queues screen.
Select a queue.
You can set initial values and options that apply to individual TCP/IP devices on the TCP/IP Queue Options screen.
Use this source device?
Specify whether to use this source device.
Yes Default for queue BARRTCP1. Use this device.
No Default for BARRTCP2 through BARRTCP4. Do not use this device.
Session name is ________
Specify the name for this TCP/IP queue. The queue name can be up to 10 characters long. The session name is used by the line printer daemon protocol. For either line printer daemon or native TCP/IP protocol, the name you enter displays as the device name on the Assign Devices screen.
BARRTCP1 is the default session name. You can change the default name by typing over it in uppercase or lowercase letters and numbers.
A warning message displays on the Barr Operation screen if a host sends a print request to BARR/PRINT for TCP/IP and the queue name in the print request does not match any BARR/PRINT for TCP/IP queue name.
Use ________ protocol
Select whether to use the line printer daemon (LPD) or native TCP/IP protocol.
line printer daemon Default. Implement the LPD protocol.
native TCP/IP Use native TCP/IP support (a standard BSD socket) only.
Process LPD control file?
Select whether to extract information from the LPD control file.
No Default. Take no information from the LPD control file.
Yes The software automatically sets the Barr file attributes of Jobname, Formname, and FCBname to the values extracted from the control file according to the Set Jobname to, Set Formname to, and Set FCBname to options.
If you set the banner option in the control file, the Barr software generates a banner from control file information. The maximum field sizes in the banner page can be as follows: jobname, 40 characters; filename, 131 characters; hostname, 31 characters; and username, 31 characters.
If you use more than one method to set file attributes, you might overwrite the attributes. See section 6.1 for more information.
Set Jobname to:
When you set Process LPD control file to Yes, the software sets the Barr file attribute of Jobname to the value you specify.
Jobname Default. Sets the job name to the UNIX job name.
Filename Sets the job name to the UNIX file name.
Hostname Sets the job name to the UNIX host name.
Username Sets the job name to the UNIX user name.
Classname Sets the job name to the UNIX class name.
Set Formname to:
When you set Process LPD control file to Yes, the software sets the Barr file attribute of Formname to the value you specify.
Filename Default. Sets the form name to the UNIX file name.
Hostname Sets the form name to the UNIX host name.
Username Sets the form name to the UNIX user name.
Classname Sets the form name to the UNIX class name.
Jobname Sets the form name to the UNIX job name.
Set FCBname to:
When you set Process LPD control file to Yes, the software sets the Barr file attribute of FCBname to the value you specify.
Hostname Default. Sets the FCB name to the UNIX host name.
Username Sets the FCB name to the UNIX user name.
Classname Sets the FCB name to the UNIX class name.
Jobname Sets the FCB name to the UNIX job name.
Filename Sets the FCB name to the UNIX file name.
Print banner page:
Specify how to respond to host banner page requests.
on request Default. A banner page prints only if the host requests a banner page with the L command in the control file.
always Always print a banner page.
never Never print a banner page. The Barr software ignores the L command in the control file from the host.
Use native TCP/IP port __________
You can specify a native TCP/IP port when you select Use native TCP/IP protocol. The default is port 9100.
Translate ASCII-to-EBCDIC in S/370 mode?
UNIX hosts and PCs use data in ASCII format; however, S/370 channel printers expect data in EBCDIC format. Use this option to translate files from ASCII to EBCDIC when you select the S/370 Channel receive mode on the destination device.
Yes Default. Translates data from ASCII format to EBCDIC format when you select S/370 Channel receive mode.
No Does no translation when you select S/370 Channel receive mode.
Emulate DPC carriage control commands?
For printers manufactured by Dataproducts Corporation, select whether to treat extended ASCII characters as characters or carriage control commands.
No Default. Sends all characters except CR, LF, FF, and TAB to the printer. Allows you to print extended ASCII characters (above character 127 in the ASCII code pages).
Yes Interprets some extended ASCII characters (above character 127 in the ASCII code pages) as carriage control commands. Use this option only if your printing application generates data for Dataproducts printers.
Use SPUR compatibility carriage control?
This option applies only if you replace a SPUR USA-II channel printer driver with BARR/PRINT for TCP/IP and the data contains dynamic job description entries (DJDEs). This option affects how the software handles carriage control.
No Default. For most SPUR conversions, you do not need this feature.
Yes Use this selection only with vertical alignment. SPUR handles vertical channel skips differently from the IBM standard that Barr software follows.
Convert tabs to spaces?
Specify whether to convert or preserve tabs.
Yes Default. Convert horizontal tabs to eight spaces.
No Preserve existing tabs.
1F enables special formats?
Choose whether to disable special format handling options. (Appendix A describes supported special formats.)
Yes Default. A 1F indicates special formatting.
No The software processes the 1F hexadecimal character as data.
To set options globally for all queues, start at the BARR/PRINT for TCP/IP Queues screen.
Select Global Options.
The Global Options screen displays.
Edit ASCII-to-EBCDIC table?
When you receive files from a TCP/IP device with the S/370 Channel receive mode and you select Yes for the Translate ASCII-to-EBCDIC in S/370 mode option on the TCP/IP Queue Options screen, the Barr software converts the data from ASCII to EBCDIC format. You can change how to translate the data by editing the table the software uses to perform the translation.
No Use the default table to translate characters from ASCII to EBCDIC.
Yes Change how to translate characters from ASCII to EBCDIC format.
If you select Yes, the TCP/IP ASCII-to-EBCDIC Translation Table screen appears.
The table arranges translation codes in columns. The left two digits in each column are current hexadecimal representations of each character. The right two digits are translations for the character. You can modify the right two digits.
Use the UP ARROW and DOWN ARROW keys to move up and down columns on the screen.
To edit an entry, place the cursor on the entry and type over it.
When you finish editing the table, press ENTER to store your changes.
To exit without saving your changes, press ESC .
This table applies to files received from TCP/IP devices only. The ASCII and EBCDIC Translation Tables option on the Tuning and Global Options screen applies to other devices. See your BARR/RJE manual or BARR/SPOOL manual for information about translation tables for other devices.
Banner page width:
You can configure the banner width when you select Banner page width. The default is 132 columns. You can set Banner page width to a value between 70 and 132.
The Banner page width size does not change the actual size of the banner in bytes.
After you complete the BARR/PRINT for TCP/IP description, you need to direct the BARR/PRINT for TCP/IP output to destination devices. Start at the Installation Description menu.
Select Assign Devices.
The TCP/IP queues you specified in the BARR/PRINT for TCP/IP Description screen appear on the Assign Devices screen as source devices. The default device names are BARRTCP1, BARRTCP2, BARRTCP3, and BARRTCP4. You can change these names on the LPD Queue Name screen.
Printing from Multiple Hosts: Assign one host to each queue, otherwise each host must compete for the queue and a host print request might be rejected. If you want to share printers among multiple hosts, assign the LPD print queues to SPOOL so that print jobs can continue to arrive when the printer is busy.
Barr RJE and BARR/SPOOL allow you to spool print files received via BARR/PRINT for TCP/IP. The following example shows you how to assign the source device BARRTCP1 to the destination device SPOOL.
Select BARRTCP1 as the source.
Select SPOOL as the destination.
Specify the file name and options. In this example, the Beginning of file name is blank and the Ending of file name is jobname. Press the PLUS SIGN key several times to select jobname.
See the Assign Devices chapter in your BARR/RJE manual or your BARR/SPOOL manual for more information about specifying the file name.
When you press ENTER, the screen shows BARRTCP1 assigned to SPOOL.
Receive mode controls how to handle files received to the PC.
Select Receive mode from the Assign Devices screen.
Receive modes display on the bottom of the Assign Devices screen.
Only three of the receive modes apply to data received from TCP/IP devices:
ASCII Default. Received file remains in ASCII format. Performs no translation. Null characters are passed through as character data.
Binary Data received from the host to the PC is not altered. Some applications require unaltered data. You cannot use control files with binary receive mode.
S/370 Channel Required for printing to an S/370 channel printer. Only used with the PRINT370 option (purchased separately) and not valid for the Xerox 4235 printer. Realia COBOL format converts data to varying length binary records.
The following example shows you how to assign S/370 Channel receive mode to the data received on printer session 1 (which has the default name BARRTCP1).
After you select the destination for the BARRTCP1 device, select Receive mode on the Assign Devices screen.
Select S/370 Channel.
Select normal or Machine for carriage control.
An asterisk (*) appears next to the destination device to indicate a Receive mode other than ASCII.
Press ENTER to continue.
The Options selection on the Assign Devices screen provides several ways to set file attributes when you receive a file. The type of device determines available options. This section discusses the options for TCP/IP devices (which have the default names BARRTCP1, BARRTCP2, BARRTCP3, and BARRTCP4). See your BARR/RJE manual or BARR/SPOOL manual for information about options for other devices.
If you use more than one method to set file attributes, you might overwrite file attributes. See section 6.1 for more information.
Options apply only to files the Barr software receives. You can set attributes for files from other sources (such as files copied into the print spool directory) with the PRT utility. See your BARR/RJE manual or BARR/SPOOL manual for information about the PRT utility.
Available options display when you select Options from the menu line at the bottom of the Assign Devices screen.
ASCII data with ASA carriage control?
Specify whether to recognize the first character of ASCII data as carriage control. This option only works with ASCII receive mode and will only affect jobs printed to S/370 channel attached printers.
No Default. Treat all ASCII characters as data and thus print all characters.
Yes Recognize the first character of ASCII data as carriage control and set a flag in the spool header.
OUTPUT statement used in file?
You can use the OUTPUT statement to specify file attributes such as job name, form name, file name, copies, priority, and class. Before the Barr software receives the file, you must add an OUTPUT statement to the file. You might need to change the host application program that produces data so it will write the OUTPUT statement to the file. See your BARR/RJE manual or BARR/SPOOL manual for the OUTPUT statement format.
No Default. Does not use the OUTPUT statement.
Yes Extracts information from the OUTPUT statement in the file and places it in the Spool file header. Remember to include the OUTPUT statement in the file before you receive it to the PC.
In the OUTPUT statement, the word OUTPUT must begin in column 1, column 7 must be blank, and the keyword for the first option must begin in column 8. The statement must fit on one line in the file. It cannot wrap to the next line. If the files maximum line length is limited to 80 characters, you might not be able to specify all the possible options.
Use these keywords to set options in the OUTPUT statement and substitute the option value for n: FILENAME=n JOBNAME=n FORMNAME=n FCBNAME=n COPIES=n PRIORITY=n CLASS=n DISP=n ASCIIASA=n. (You cannot abbreviate the keywords.) You can list the options in any order. Specify only the options you need. For example:
OUTPUT FORMNAME=taxes FILENAME=taxdata
Do not confuse the Barr OUTPUT statement with the job control language (JCL) OUTPUT statement, which has a different use.
You cannot use both the Barr OUTPUT statement and a control file. You must use one method or the other.
Class: n
Use this option to automatically assign a new class to files received on a given source device. You can set the class for each source device. Default classes are 1 for the first TCP/IP device (BARRTCP1), 2 for the second TCP/IP device (BARRTCP2), and so forth.
Spool header from data?
This option allows you to extract a files formname or jobname from a text line within the file. You can use this option with files input through any source device (except COMMAND, LOG, or SPOOL1 to SPOOL8) if the receive mode is ASCII, S/370 Channel, or Binary. The information to extract must occur at the same location in every file.
You cannot use both Spool header from data and a control file. You must use one method or the other.
No Default. The software does not extract formname or jobname information from the file.
Yes The software extracts formname or jobname from a specified location in the file and places it in the Barr file header. If a formname or jobname already exists in the file header, the software replaces it with the value obtained from the file text. When you press ENTER, you must select formname or jobname and specify the page, line, and column numbers where this information appears in the text.
If a file contains no form feeds (FF), the software searches only the first 200 lines in the file for the specified spool header information.
When you extract the name from the specified location:
The software skips leading blanks.
The software terminates the file name if it detects a blank after a valid character in the column range. For example, if the software finds DAILY RPT at the specified location, the file name will be DAILY.
Ignore _____ lines from start of file
Use this option to delete a specified number of lines from the start of a file when you receive the file. The maximum value is 32,767 lines.
Strip spool header?
When you write files to disk, you can remove spool headers from the files. This option only displays when the destination is SPOOL or (FILE). If you strip the spool header when the destination is SPOOL, the file has no header information and is assigned a class of Z. The most useful application is to set the option to Yes for SPOOL1(FILE) so the print spool uses the header information to route the file via a spool printer (SPOOL1), but does not preserve the header in the final destination on disk.
No Default. Do not strip the spool header.
Yes Remove the spool header from the file.
Select Exit and Save Changes from the Installation Description screen when you finish configuring the software.
Select Exit and Save Changes.
Save your changes to the program file or a configuration file.
After you install the ETHERNET2 or ETHERNET PCI adapter, configure the adapter driver, configure the FTP software PC/TCP kernel, and configure the Barr software, you should be able to access your TCP/IP network and receive LPR print streams.
Use the ping command to verify your connection to the TCP/IP network. If you accessed the network after you installed the PC/TCP kernel, you need to check the connection again. See section 5.2 for an example.
When you connect to the TCP/IP network, you should receive a host responding message and be able to receive LPR print streams with the Barr software. See your BARR/RJE manual or BARR/SPOOL manual for Barr software operating instructions.
If the host does not respond, you might have a Barr software configuration problem. Contact Barr Technical Support.