This topic contains solutions to common problems that you might experience with BARR/PRINT TCP/IP.
Cannot receive data using Print Utility or BARR/PRINT TCP/IP
Errors occur when importing files that require ASCII to EBCDIC conversion
An incorrect class value is received from the host device using LPD
Cause: This problem occurs when one Barr computer is printing through LPR to an LPD queue on another Barr computer. The BARR LPD service on the receiving Barr computer is not started. So when LPR tries to write to it, Windows error messages appear on the sending computer.
Solution: Start the BARR LPD service on the receiving Barr computer to resolve the problem. To prevent this problem from reoccurring, you may want to configure the Barr LPD service to start automatically. For more information about configuring services to start automatically at computer startup, open the Services utility and click Help.
Cause: The BARR LPD service has not been started or is configured to start manually.
Solution: Start the BARR LPD service or configure the service to start automatically.
Cause: The BARR LPD service is discarding the job because the output statement options on the BARR/PRINT TCP/IP Options tab have been selected incorrectly. (The Keep prior data option is not selected and there is not an output statement in the data.)
Solution: On the Options tab, select Keep prior data or disable the output statements feature.
Cause: The control file sent through LPR does not contain a field for the form name.
Solution: The control file contains fields for class, host name, and job name. You can populate one of these fields with the form name and use an override table to move the value into the form name field.
Create an override table using the following guidelines.
You do not need to create a condition statement.
Create an action statement that sets the Data Set Header General Section NDHGFORM - Form name field equal to a LPD/User Custom Section field that is the source of your form name (in the control file).
When the job is sent, the value of the specified field automatically will be moved into the form name field.
Cause: The most likely cause is that the data type has been set incorrectly (for example, the data type is set as Xerox Metacode when the data is in Barr S/370 format). Another problem might be that the data is corrupt, the line is too long, or the same file contains more than one data type.
Solution: Verify that the data is in the intended format and that the data type is set for the incoming device. If your data is coming from a Barr DOS system, the correct option is usually Barr DOS (ASCII or S/370). Check the operator console for more information. See the Format tab help topic for more information.
Cause: Barr Enterprise Print Server was installed as a system account on a computer, which is part of a network or workgroup.
Solution: Reinstall Barr Enterprise Print Server as a user account.
Cause: LPD is not configured correctly to transmit files if the host device is using the LPR-V switch and the control file is transmitted last.
Solution: Set up a print queue for each file type you will be receiving. For example, ASA files will have a print queue titled ASAFiles, with a <Default> LPR command that is configured to receive ASCII with ASA carriage control files.
Cause: The selected file format conflicts with the actual file record structure.
Solution: Many programs generate Metacode data for Xerox printers. To receive this data over TCP/IP using the LPR/LPD protocol, a queue must to be correctly configured to receive the Metacode data. First, determine the record structure of the file: Barr S/370 or VBM Acronym for Variable Blocked with Machine carriage control. This is a standard mainframe file format.. The most common is VBM. Once the file record structure is known, define a queue to accept the Metacode data.
Determine the record format.
Add an LPD print queue.
Configure the <Default> LPR control file command to receive one of the following file types.
If the file type is VBM, select VBM and Xerox formats.
If the file type is Barr S/370, select Barr DOS (ASCII or S/370).
Cause: Most LPD services monitor the TCP/IP port 515 (RFC1179.) The BARR LPD service cannot start if another service or program is controlling port 515. This cause assumes that the Microsoft Windows TCP/IP print services are installed, the Barr LPR port works, and it is possible to ping Acronym for Packet Internet Groper. A protocol for testing whether a particular computer is connected to the Internet by sending a packet to its IP address and waiting for a response. other devices on the network.
Solution: Disable all LPD services and programs except the BARR LPD service. Barr Systems provides a version of LPR with the Barr Enterprise Print Server. If you want to use our LPR instead of Microsoft LPR, remove the Microsoft TCP/IP printing service. To do this, open the Network utility. From the Services tab, select the Microsoft TCP/IP printing service and click Remove.
Cause: The NDHDBCLS value in the control file is incorrect. The first letter of the NDHDBCLS value must match the NDHGCLAS value.
Solution: Complete the following steps to verify that the NDHDBCLS field contains the appropriate value.
Open the Spool Window.
Right-click the appropriate document and select Properties.
Click the plus sign (+) next to Data Set Header, and then click the plus sign (+) next to Data Set Header LPD/User Custom Section.
The first letter of the NDHDBCLS - Banner class value should match the NDHGCLAS - Class value in the Data Set Header General Section. If the value for NDHDBCLS is incorrect, ask the host operator to modify the control file.
See also: Mapping control file fields to header fields