Troubleshooting: Communication scope characters

BARR/RJE

This topic contains explanations for common BARR/RJE communication scope messages.

"RrRrRrTRrTRrRrT" characters appearing in the communication scope

Cause: The telephone company might be experiencing line problems.

Solution: Contact the telephone company to have the line checked.

See also: Communication scope characters

"NNN" characters appearing in the communication scope

Cause: The Barr software is not recognizing the frames it is receiving.

Solution: On the RJE Configuration Utility's Communication Link tab, click NCP. In the NCP Definition for Nonswitched Line dialog box, view the NRZI and PU macro values. Speak with the host programmer to make sure these values match the values in the host's VTAM/NCP definition. If these values are correct, check the Barr SDLC adapters by running the appropriate loopback tests.

"TestTestrXidTXidT" characters appearing in the communication scope

Cause: The 3174 cluster controller has not been updated with the MAC Acronym for Media Access Control. In the IEEE 802.x specifications, the lower of two sublayers that make up the ISO/OSI data link layer. address of the BARR/RJE network adapter, or a locally administered address is required.

Solution: Ask the host programmer to perform one of the following solutions.

Update the 900 table in the 3174 with the MAC address of the computer's network adapter.

Supply the customer with a locally administered address to use.

"TestTTestT" characters appearing in the communication scope

Solution 1

Cause: The LOCADD value on the 802.2 Connection Configuration dialog box is set incorrectly for the FEP MAC Acronym for Media Access Control. In the IEEE 802.x specifications, the lower of two sublayers that make up the ISO/OSI data link layer. The MAC manages access to the physical network, delimits frames, and handles error control. address.

Solution: Ask the host programmer for the correct LOCADD value for the FEP MAC address and correct the setting.

Solution 2

Cause: Network routers might not have the Source Route Bridging (SRB) feature enabled and network routers may not be forwarding the BARR/RJE 802.2 frames to the host network.

Solution: Ask the network router analyst to check the settings on the routers to ensure that the SRB feature is enabled and that the BARR/RJE 802.2 frames are being forwarded correctly to the host network.

Solution 3

Cause: The wrong TIC address has been entered in the RJE Configuration Utility.

Solution: Make sure the LOCADD value is the address of the controller TIC. A common mistake is to enter the TRN address of the local computer instead. To correct the TIC address, on the RJE Configuration Utility's Communication Link tab, select the 802.2 LLC2 link and click Configure. From the 802.2 Connection Configuration dialog box, type the correct value in the LOCADD box.

"Rr!" characters appearing in the communication scope

Cause: BARR/RJE has received an illegal or unformatted error that it cannot understand.

Solution: Complete the following steps to resolve the error.

Rule out a hardware problem by running the appropriate hardware diagnostics: CHANNEL-OUT and SDLC. Verify that the modem is running in synchronous Occurring at the same time. In computer transmissions, a reference to activity governed by a clock or by synchronized timing. mode.
Eliminate any problems with the software configuration by comparing the settings on the RJE Description tab and Communication Link tab with the host definition settings.
Make sure there is no polling address duplication with another device on the sharing unit. Do this by shutting down the other devices sharing the line and see if BARR/RJE functions correctly. If BARR/RJE does function correctly, then another device has the same polling address.

"XidTXidT" characters appearing in the communication scope

Cause: The IDBLK and IDNUM values specified in the BARR/RJE configuration do not match the values specified in the VTAM PU definition. If these values do not match, VTAM will refuse the connection, treating it as a connection coming from an invalid switched major node.

Solution: Ask your host programmer for the correct IDBLK and IDNUM values. To configure the Barr software with these values, on the RJE Configuration Utility's Communication Link tab, click Configure. Depending on your connection, the 802.2 Connection Configuration dialog box or the SDLC Connection Configuration dialog box displays. Type the correct values into the IDBLK and IDNUM boxes. For more information, see the Communication link parameters topic.

"E22" characters appearing in the communication scope

Solution 1

Cause: Network analysts made changes to the network. The communication scope message, E22, indicates that the BARR/RJE Xid poll frame is not being opened by any other device on the network.

Solution: The network analyst must verify that the Source Route Bridging (SRB) feature is enabled on the routers. The Address Recognition and Frame Copy bits must be set by the router on the original frame. A network Sniffer trace may be needed.

Solution 2

Cause: The networking software transmitted a packet of data which was never received. The software believes that the data was never received because the Address-Recognized and Frame-Copied indicators in the Frame Status field were not set properly when the packet returned to the system. This can be caused by a problem in the network adapter, preventing the data from being received properly. The problem might be the result of a faulty network adapter or an incompatibility between the adapter and the system.

Solution: Replace the network adapter.

"TTT" characters appearing in the communication scope

Solution 1

Cause: The router port is not configured correctly. The Barr SDLC adapter appears as a dedicated SDLC device to the route; therefore, the router must be coded with appropriate values that the mainframe expects on its end, such as ADDR, IDBLK, or IDNUM.

Solution: Barr SDLC adapters with standard cables need to connect to a DCE Acronym for Data Communications Equipment. port on the router, not a DTE Acronym for Data Terminal Equipment. port. The router SDLC port needs to be configured as DCE, or the standard Barr cable must be replaced with a Barr SME cable.

Solution 2

Cause: The host PACING and MAXOUT settings for the remote are incorrect.

Solution: Ask the host programmer to verify that the host's remote settings are correct. The PACING, VPACING, and MAXOUT settings at the host must match the remote MAXOUT setting in the SDLC Connection Configuration dialog box.

Solution 3

Cause: Asynchronous Pertaining to, being, or characteristic of something that is not dependent on timing. For example, asynchronous communications can start and stop at any time instead of having to match the timing governed by a clock. modems, like the US Robotics Sportster line of modems, are not supported by the Barr software. The mainframe environment requires synchronous Occurring at the same time. In computer transmissions, a reference to activity governed by a clock or by synchronized timing. communication connections. A Multitech Multimodem (with synchronous support), the USR Courier V.Everything, and other similar modems do support synchronous communications.

Solution: Use a modem that supports synchronous communications. If you are uncertain whether the modem you currently have is a synchronous modem, contact the modem manufacturer or visit www.modemhelp.org for more information. If you have an asynchronous modem, you can contact Barr Systems to purchase a synchronous modem.

Solution 4

Cause: Host is not polling/Line not started in VTAM

Solution: Check the host and reset the line.

Solution 5

Cause: NRZI is set incorrectly in the Barr software.

Solution: Enable or disable the NRZI option, depending on how the option is currently set.

Solution 6

Cause: The VTAM PU macro's IDBLK and IDNUM values are incorrect in the Barr software.

Solution: Ask the host programmer for the correct values. For more information, see the Communication link parameters topic.

To compare and correct the IDBLK and IDNUM values in the Barr software, on the RJE Configuration Utility's Communication Link tab, click Configure. Depending on your connection, the 802.2 Connection Configuration dialog box or the SDLC Connection Configuration dialog box displays. If the IDBLK and IDNUM values do not match the settings on the host, type the correct values into the IDBLK and IDNUM boxes.

Solution 7

Cause: There is a cable problem or the adapter is not properly seated

Solution: Check the cables and make sure the adapter card is well-seated.

Solution 8

Cause: The modem is not software-compatible or is not set up properly.

Solution: Check the modem to ensure that it is compatible with the BARR/RJE software. The modem must be a synchronous modem, not an asynchronous modem. If you are failing to connect with a US Robotics (USR) Courier V.Everything mode, make sure all settings on the modem are set according to the USR Courier V.Everything Settings document.

If you are having problems getting Hayes Optima 33.6 modem to connect, make sure the settings are correct. This problem does not occur with the Hayes Optima 56K or 28.8K. The Hayes Corporation, however, is now out of business, and this brand of modems is no longer available. Please contact your Barr Systems sales associate for replacement modem recommendations.

To improve the Hayes Optima 33.6 modem's performance, use the Not autodial option in the BARR/RJE software. On the RJE Configuration Utility's Communication Link tab, click Configure. From the SDLC Connection Configuration dialog box, select Not autodial.

Store the phone number internally in the modem. This will allow the modem to dial as soon as the Barr software raises the DTR signal.