Troubleshooting RJE Communication scope characters

This topic contains explanations for common RJE communication scope messages.

See also:


"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

"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 RJE network adapter, or a locally administered address is required.

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

OR

See also: Interpreting RJE diagnostic data

"Rr!" characters appearing in the communication scope

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

Solution: Complete the following steps to resolve the error.

  1. 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.

  2. 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 RJE functions correctly. If RJE does function correctly, then another device has the same polling address.

"E22" characters appearing in the communication scope

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.