This topic contains solutions to common problems that you might experience with BARR/PRINT CHANNEL.
Metacode jobs received with Print Channel do not print correctly
BARR/PRINT CHANNEL CAB does not stay enabled when sending jobs from a SPUR box
Cause: The adapter is currently being used by one or more connections.
Solution: Before you can run hardware diagnostics, all connections using the adapter must be stopped. Stop all connections using the adapter, and then run hardware diagnostics again.
Cause: In the printer definition on the host, the TRANS parameter might be set to YES causing non-printable characters (that is, binary data) to be converted to blanks.
Solution: Change the printer definition on the host to TRANS=NO.
Cause: Some host computers require that BARR/PRINT CHANNEL enforce UCS encoding.
Solution: Complete the following steps to enforce UCS encoding.
From the BARR/PRINT CHANNEL window right-click the appropriate connection and select Properties.
From the Communications
tab, click Advanced. The Advanced Properties dialog box
displays. 
Under UCS size, select Limit byte length to and specify the appropriate UCS size.
Click OK.
Cause: On a VSE/POWER An S/390 operating systems program that simultaneously operates many readers, printers, and remote communications devices. host, if an FCB for a job is 45 lines or less, the host will not print the block letters on the banner page. The host will only print the pertinent start and job information. The host will also shorten the typical two-page banner to one page. Because the length of the banner page is now less than 45 lines, the banner page detection search string, usually found on lines 50 and above, changes, causing the banner not to be detected.
Solution: Configure a second banner for jobs with an FCB length less than 45 lines. Banner page recognition can then be set up to recognize one-page banners without the block lettering. See the Banner Configuration dialog box for more information.
Cause: BARR/PRINT CHANNEL is set to a default data transfer rate of PROTOCL=D (DCI High Speed Transfer (HST)), also known as Four-Tag or Double-Tag. SPUR does not support this transfer rate, and instead selects a Two-Tag (also known as DCI Single Tag) transfer rate.
Solution: Complete the following steps to set the adapter channel transfer mode equal to the rate of the SPUR box.
Open the CHANNEL-IN utility.
From the Configuration tab, select Properties. The Adapter Properties dialog box opens.
In the Channel transfer mode list, select PROTOCL=D (DCI Single Tag).
Click OK.