Troubleshooting

This topic contains solutions to common problems that you might experience with BARR/CHANNEL Offload.

• No messages are written to the Operator Console

• Unable to run hardware diagnostics

• CHANNEL CAB does not stay enabled when sending jobs from a SPUR box

See also:

• Overview

• Getting started

• Common questions

No messages are written to the Operator Console

Cause: The priority level affects what displays on the Operator Console. If the priority level of selected modules is set to Critical, then only errors that halt execution will be written to the Operator Console.

Solution: When you capture a trace, the Operator Console priority level should be something other than Critical.

We recommend setting priority levels to Informational. You must only select a technical level if advised to do so by a Barr Support analyst.

Unable to run hardware diagnostics

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.

CAB does not stay enabled when sending jobs from a SPUR box

Cause: BARR/CHANNEL Offload 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.

1. Open the CHANNEL-IN utility.

2. From the Configuration tab, select Properties. The Adapter Properties dialog box opens.

3. In the Channel transfer mode list, select PROTOCL=D (DCI Single Tag).

4. Click OK.