This topic contains solutions to common problems that you might experience with BARR/PRINT390.
Last page of job does not print until END Command is issued or a new job is started
BARR/CHANNEL-OUT utility does not show the serial number of the PRINT390 adapter
Receiving "Unable to query when using Find Devices" error message
DJDE prints as data on the page and is not recognized by printer
Cause: The Windows spooler service is started. This must be stopped before you can run hardware diagnostics.
Solution: Stop the Windows spooler service, and then run hardware diagnostics again.
Cause: Print370 (DOS) has the option to vary the printer offline, BARR/PRINT390 (Barr Enterprise Print Server) does not. Prior to activating the channel switch, the printers must be put in an offline state.
Solution: Because BARR/PRINT390 communicates with the printer through spooler service, you can vary the printer offline by stopping the spooler service.
Stop the Windows spooler service.
Alter the switch setting to activate the correct printer.
Start the Windows spooler service.
Cause: The BARR/CHANNEL-OUT Find Devices tab might return a printer type of Unknown and a sense condition of 80_00_00_00_00 when querying some printers. This is not an error because some channel-attached printer models do not recognize the channel commands issued by the Find Devices tab. The return of a sense condition indicates that there is a device located at the channel address, but the microcode in the channel device controller does not recognize the more advanced channel commands used by the Find Devices tab. Regular printing to that device will not be affected.
Solution: Continue to configure and test the channel printer. After configuring the channel printer, print one of the sample print jobs as a functional test of the printer. If the sample job prints correctly, then the printer is configured properly and is functioning correctly. Refer to the Getting started help topic for more information.
Cause: The Barr ASCII driver cannot be used to send ASCII data to channel-attached printers. The data type sent to channel printers is controlled by the code page the printer is configured to use, not by the driver. You must always use the Barr PRINT390 driver with BARR/PRINT390.
Solution: Change the Windows PRINT390 printer to use the Barr PRINT390 driver, and set the proper code page for the printer in the Configuration Utility.
Modify the printer driver. Change it to the Barr PRINT390 - printer driver.
Open the Configuration Utility.
On the Spool Printers tab, select the Print390 printer and click Modify.
Click Advanced. The Advanced Printer Options dialog box displays.
Under Code page, select the correct code page. For example, use 37 for EBCDIC and 437 for ASCII.
Click OK three times to exit.
Cause: The Bus & Tag cable Cables used to connect devices to mainframe channels. The bus cable transmits data and the tag cable controls information on the bus. connection is loose or a pin is bent. This can have an unpredictable effect on all print jobs.
Solution: Tighten all cables, check for bent pins, and perform loopback A testing procedure in which transmitted data is returned as received data. diagnostics again.
Cause: The Xerox printer is looking for a trailer page to indicate that it has reached the end of a job. The trailer on the job is different from the one being looked for, so the printer never identifies it as the end of a job and does not print the last page.
Solution: Talk to a Xerox analyst about changing the search criteria for a trailer page, or modify the Banner created by the Barr Enterprise Print Server to include the same criteria as the previous banner page.
Cause: There is a hardware conflict that is preventing the driver from detecting the adapter. On the HP Vectra, this appears to be a conflict with the Video Card using IRQ9.
Solution: Complete the following steps:
Enter the HP Vectra's BIOS Acronym for Basic Input/Output System. Program permanently stored in read-only memory (ROM) chips on your PC’s system board. and disable the Plug and Play BIOS.
Reserve IRQ9 so that no device will use it.
Restart the computer and run the loopback test on the Barr adapter to verify that the conflict has been resolved.
Cause: The computer's registry was not correctly updated after the CHANNEL-OUT device driver was added.
Solution: Restart the computer to complete the driver installation.
Cause: The Barr PRINT390 port requires the Barr PRINT390 drivers. The use of any other driver with the Barr PRINT390 port will produce unpredictable results.
Solution: Delete the Barr PRINT390 port and recreate the port and the printer using the Barr PRINT390 driver.
Cause: The printer might not be set up in IBM 3800 compatibility mode.
Solution: Contact Océ for necessary software to set the printer up in IBM 3800 compatibility mode. Océ also must provide the SNPFORM A Siemens Nixdorf printer utility used to create forms from a list of resources. and SNPIMAGE A Siemens Nixdorf printer utility used to create resources from a list of commands. utilities to set up the FCB overlays required by the printer. After initial setup, the file must be converted to the format required by the Barr Enterprise Print Server using the Resource Conversion Utility.
Cause: The BARR/PRINT390 driver is not installed.
Solution: Install the CHANNEL-OUT device driver.
Cause: There is a cable problem or the adapter is not properly seated.
Solution: Run the loopback test. If it passes, make sure that the card is seated properly.
Cause: The PRINT390 adapter is bad.
Solution: Replace the adapter.
Cause: The printer's properties are not set correctly.
Solution: Enable the Print directly to the printer setting in the printer's properties.
Cause: The Find Devices operation is unable to communicate with the channel device because another program has control of the device address.
Solution: Complete the following steps to enable communication.
Close any other programs that may be using the channel device driver.
Open the BARR/CHANNEL-OUT utility.
From the Find Devices tab select the adapter, and then click Find.
Start the Windows spooler service.
Cause: The DJDE will print as regular print data if the IDEN Prefix, Skip, and Offset do not match the format specified in the printer's JSL.
Solution: Complete the following steps to verify that the DJDE in the print data is in the exact format specified in the printer's JSL.
At the Xerox console, take the printer offline Logically (or physically) disconnected and unable to communicate with the host computer. by typing OFF.
Confirm the logon level is 3 at the Xerox printer by typing LOG 3.
Type TYPE followed by the name of the start JSL that will be used (for example, TYPE DFAULT.JSL).
Make a note of the prefix string, skip, and offset. See the following example.
IDEN PREFIX='$DJDE',SKIP=10,OFFSET=1,OPRINFO=NO;
A prefix preceded by an A indicates that the
character string will be sent as ASCII.