Interpreting RJE diagnostic data

RJE Diagnostics utility

The RJE Diagnostics utility provides diagnostic data that you can use to troubleshoot your RJE connection. The three types of diagnostic data are explained in this topic.

What do you want to do?

Use the RJE Diagnostics utility

Learn about the RJE Diagnostics window

Communication scope characters

To view the communication scope, open the RJE Diagnostics utility. To display or hide the communication scope, on the menu bar, select View | Communication Scope. The communication scope is refreshed when the program starts, or when you select View | Reset on the menu bar.

The communication scope characters vary depending on your connection type and whether you are viewing the communication scope in color or monochrome. You can use either character color or position to learn more about the communication.

In the color mode, colors indicate whether the activity comes from the computer or the mainframe. The colors that display match the colors configured in the RJE Console window. By default, when BARR/RJE sends a message to the mainframe, green characters appear and when BARR/RJE receives a message, magenta characters appear. In the Help, the sent message appears in normal text and the received message appears in reverse video (white text with a black background). For a dial-up connection, dial-up scope characters display in white.
In the monochrome mode, the placement of the characters indicate whether the activity comes from the computer or the mainframe. When BARR/RJE sends a message to the mainframe, the characters appear across the top of the communication scope. When BARR/RJE receives a message, the characters appear across the bottom of the communication scope. In the Help, the sent message appears in normal text and the received message appears in reverse video (white text with a black background). For a dial-up connection, dial-up scope characters display across the middle of the communication scope.

Dial-Up scope characters

To follow BARR/RJE’s progress while it tries to connect to the mainframe, watch the communication scope. Dial-up scope characters display in white. For instance, you can see if BARR/RJE dialed the phone number, if there was no answer, or if the line was busy. Dial-up scope characters are explained in the following table.

Character	Description
A	Answer tone. Host modem sent answer tone to remote.
B	Busy. Host modem is busy.
D	Dialing. Modem is in the process of dialing.
N	No answer. No answer tone has been detected. Modem redials.
R	Ringing. Host modem is ringing.

Dial-up scope characters usually appear in sequences on your communication scope. The following are some examples.

DB – Dialing, Busy
DRA – Dialing, Ringing, Answer
DRND – Dialing, Ringing, No answer, Redialing

802.2 LLC2

After the computer connects to the mainframe, the remote goes into Normal Response Mode (Snrm on the communication scope) and data communications begin. Characters on the communication scope reflect activity between the computer and mainframe.

Communication scope characters

Character	Description	Notes
0-7	Information frame	Frame number.
A	Open	Open the token ring adapter. Only performed if it is not already opened.
C	Connection established	802.2 LLC2 connection has been established.
Enn	Error status returned from computer token ring adapter	The codes (nn) are defined in Adapter Check Reason Codes in the Local Area Network Technical Reference (IBM SC30-3383-2). E09 – Adapter not initialized. E0C – Adapter not opened. E22 – No response from host. E28 – Token ring adapter opened, but transmit buffers too small for MAXDATA of 1033. E43 – SAP already in use. E46 – Resources unavailable.
Frr	Frame reject received	A frame reject has been received. The five-byte reject information is included in the scope. This indicates a link level protocol violation was detected by the remote link station. One possible violation is an incompatible frame size between partners. Check that MAXDATA set in BARR/RJE matches MAXDATA set for the mainframe (or controller, if attached to a 3174 Controller). See the Communication link parameters topic for more information about MAXDATA.
Frs	Frame reject sent	A frame reject has been sent. The five-byte reject information is included in the scope. This indicates a link level protocol violation was detected by the remote link station. One possible violation is an incompatible frame size between partners. Check that MAXDATA set in BARR/RJE matches MAXDATA set for the mainframe (or controller, if attached to a 3174 Controller). See the Communication link parameters topic for more information about MAXDATA.
I	Initialize	Initialize the token ring adapter. Performed only if it is not already initialized.
L	Open link station	Allocate a link station before making a connection when in host mode.
Pc	Computer error	Indicates a hardware error.
Ring	Ring error	The Adapter has detected a token ring error.
Rnr	Receive not ready	Local station or remote partner has entered a local busy state, which is caused by a low buffer condition.
Rr	Receive ready	Local busy state has cleared.
S	Open SAP	A service access point is being allocated and opened.
Sabme	Set Asynchronous Balanced Mode Extended	A request for connection was received from the host.
Stat	Status request	E09 and E0C are valid normal responses. A different status might indicate adapter errors.
T	Timeout	No response from the host adapter.
Tests	Initial test command with source routing	The local ring test failed, so an all routes broadcast DLC TEST command was issued.
Testsr	Host response	A response from the host was received.
Undf	Undefined	An unrecognized frame was received. This should never occur.
Xid	Exchange identification	After the remote sends Xid to tell the host that it wants to make a connection, host sends Xid to request identification of remote.
Xidr	Exchange identification response	Remote sends identification data IDBLK and IDNUM. This data defines a switched PU in a VTAM library.
Xidrz	Exchange identification response	Controller responds with routing information.
Xidz	Exchange identification	Remote sends Xidz to host Controller Address to request routing information.

802.2 examples

StatIASXidzXidrzXidXidXidrC00

If the adapter was not previously opened, this is a normal connection. IA indicates initialization and open.

StatSXidzXidrzXidXidXidrC00

If the adapter was opened by other software (for example, network software), this is a normal connection.

StatSXidzE22

The host LOCADD entered on the 802.2 Connection Configuration dialog box cannot be located on the ring.

StatSE46

Resources are not available to open a SAP. When the adapter was first opened by LAN software, not enough memory was reserved.

StatIASXidzXidzXidz

No response from the host. Check LOCADD on the 802.2 Connection Configuration dialog box for the address of the host adapter, otherwise, check for a route problem.

StatIASXidzXidrzXid

If you are connecting to a 3174, check Q940 in the controller setup to ensure that the Barr device is defined.

HPR/IP

After the computer connects to the mainframe, characters on the communication scope reflect activity between the computer and mainframe.

Communication scope characters

Character	Description	Notes
0-7	Information frame	Frame number.
C	Connection established	HPR/IP connection has been established.
Xid	Exchange identification	Remote sends an initial Xid.
Xid3	Exchange identification	After the remote sends Xid3 to tell the host that it wants to make a connection, host sends Xid3r to request identification of remote.
Xid3r	Exchange identification	After the remote sends Xid3 to tell the host that it wants to make a connection, host sends Xid3r to request identification of remote.

HPR/IP examples

XidXid3rXid3Xid3rXid3C00

This is a normal connection.

XidTXidTXidTXidTXidT

No response from the host. Check the host name or IP address on the Link tab for the address. Otherwise, check for a route problem.

SDLC

Communication scope characters

Character	Description	Notes
0-7	Information frame	Frame number.
Disc	Disconnect	Host sends Disc to force remote into Normal Disconnect Mode.
Dm	Disconnected mode	When the remote is in Normal Disconnect Mode and the host sends frames the remote cannot process, the remote sends Dm to request an Snrm. This will only occur when program restarts.
Frmr	Frame reject	Frame was not formatted correctly. This should never occur.
Rej	Reject	Sender of the Rej has received an information frame out of sequence and is asking for it to be sent again. This is only used for full-duplex communications.
Rnr	Receive not ready	Sender is unable to receive any information frames.
Rr	Receive ready	Sender is ready to receive information frames. During idle periods, Rr messages bounce back and forth. Extra Rr messages could indicate that the Barr software is set for full duplex (DATMODE=FULL), but the host is set for half duplex (DATMODE=HALF). See the Communication link parameters topic for more information about DATMODE.
Snre	Set normal response mode extended	Host sends Snre instead of Snrm for modulo 128 sequence numbering. See the modulo 128 discussion later in this section.
Snrm	Set normal response mode	Host sends Snrm to remote setting Normal Response Mode.
Ua	Unnumbered acknowledgment	Positive response to an SDLC mode-setting command such as Snrm.
Undf	Undefined	An unrecognized frame was received. This should never occur.
Xid	Exchange identification	Host sends Xid to request remote identification.
Xidr	Exchange identification response	Remote sends identification data IDBLK and IDNUM, which define a switched PU in a VTAM library.
!	Illegal	When this follows a received frame (for example, Rr!), the frame is not formatted correctly or is illegal in this mode. This will only occur when the program restarts.

Communication scope characters indicating errors

Character	Description	Notes
A	Abort	Frame ended with 1111111 (seven or more consecutive 1s), not with a frame character.
C	CTS failure	Clear-To-Send signal is not available from modem.
E	Error with Cyclical Redundancy Check (CRC) of frame	CRC computed on bits in frame received does not agree with CRC value of frame sent. For example, noise on the telephone line could cause a bit to be lost in the frame. The SDLC protocol causes the frame to be re-sent.
F	Send failure	Transmit clock signal is probably not available from modem.
N	Non-productive receive	None of the frames received in the last 5 seconds match the SDLC address or they were random noise frames.
Q	Queue overflow	More frames received than buffers available.
T	Timeout	No answer occurred for 3 seconds. Numerous timeouts could indicate that the Barr software is set for DATMODE=FULL, but the host is set for DATMODE=HALF. See the Communication link parameters topic for more information about DATMODE.
V	Overrun of receive buffer	The ending frame character was not found before buffer was filled.
X	Equipment error	Send underrun or receive overrun. This is usually caused by LAN or hard disk turning off interrupts. Try changing the Interrupt request in the software. (For older adapters, such as the BARR/3, try setting Use DMA for communications to Yes. Your Barr adapter manual discusses this option.) If this error is related to typing on the keyboard, use the TSR program BIOS_KEY included with the Barr reference files. BIOS_KEY briefly turns off interrupts.

SDLC examples

DRAXidXidrSnrmUaRrRr00

A normal dial-up sequence.

DRAEETTTTTT

Modem answered but NRZI probably needs to be changed. See the Communication link parameters topic for more information.

DRAXidXidrTTTTT

The Xid failed. Probably IDBLK and IDNUM are not correct. See the Communication link parameters topic for more information.

RrRrRrRrRrRr

Line is idle. No information frames are being exchanged.

0123456RrRr7012345RrRr

Host is sending information. Remote is idle.

01234Rr4567012Rr5670123Rr

Both the host and remote are sending information.

012E456RrRr3456701RrRr

Frame 3 received in error. Communication resumed at frame 3.

Dedicated line examples

SnrmUaSnrmUa

BARR/RJE can hear the host but the host cannot hear BARR/RJE. Try enabling Constant RTS when configuring the SDLC link.

TTTTT

Try changing NRZI and then check your modem connection. See the Communication link parameters topic for more information.

Modulo 128

The communication scope tells you if the mainframe is operating in modulo 8 or modulo 128 mode. At log on, the host sends Snrm for a modulo 8 link or Snre for a modulo 128 link.

If the computer does not have enough memory, the software might send only seven frames at a time (as if it was in modulo 8 mode). This can occur even if you set the mainframe parameters to use modulo 128 and you see an Snre on the communication scope. A Q or an Rnr on the communication scope indicates low memory. You also might see the More memory needed for buffers message on the RJE Console. Try increasing the Memory allocated for buffers option by MAXOUT * 1024. As MAXOUT increases, so do the requirements for buffers. See the Communication link parameters topic for more information.

MS/LUA

While the computer connects to the mainframe, the communication scope remains blank.

Communication scope characters

Character	Description	Notes
0-7	PIU (Path Information Unit)	Represents frames of data.

Link statistics

Link statistics provide information about communications activity. These statistics help you evaluate the communications line’s reliability and use.

To view link statistics, open the RJE Diagnostics utility. To display or hide link statistics, on the menu bar, select View | Link Statistics. Link statistics are refreshed when the program starts, or when you select View | Reset on the menu bar.

The link statistics vary depending on your connection type.

802.2 LLC2 and HPR/IP

If you have an 802.2 LLC2 connection, you will see the following link statistics.

Statistic	Description
Lines transmitted	Total number of data lines the Send command or LAN connections read and BARR/RJE sends to a destination.
Lines punched or received	Number of data lines received on the host print or punch stream to the Barr computer.
Active SNA sessions	Number of SNA RJE sessions currently active, including printers, punches, readers, console, and commands from the keyboard.
Frames transmitted	Number of 802.2 LLC2 frames sent to the host.
Frames received without errors	Number of 802.2 LLC2 frames received without errors.
Frames discarded	Number of frames lost.
Times data lost	Number of times a frame was only partially received, usually because the frame exceeded the buffer size.
Transmit errors	Number of 802.2 LLC2 frames received with either CRC errors or frames shorter than two bytes indicated by an E on the communication scope. Number of times an error was reported requiring BARR/RJE to retransmit the frame.
Timeouts	Number of times a response was not received within the 802.2 timeout period.
Largest frame received	Size of the largest frame received. Comparing this value to the bind data will help to determine if the equipment between the host and BARR/RJE has been configured for a large enough frame size.

SDLC

If you have an SDLC connection, you will see the following link statistics.

Statistic	Description
Lines transmitted	Total number of data lines the Send command or LAN connections read and BARR/RJE sends to a destination.
Lines punched or received	Number of data lines received on the host print or punch stream to the Barr computer.
Active SNA sessions	Number of SNA RJE sessions currently active, including printers, punches, readers, console, and commands from the keyboard.
Frames transmitted	Number of SDLC frames sent to the host.
Frames received without errors	Number of SDLC frames received without errors.
Frames received with errors	Number of SDLC frames received with either CRC errors or frames shorter than two bytes indicated by an E on the communication scope.
Undefined frames received	Frames received by BARR/RJE that have an illegal SDLC control field or that are illegal in the current SDLC mode. Indicated by an ! on the communication scope.
Frames that overflowed buffer	Number of SDLC frames whose size exceeded the Barr communications buffer. Usually caused by an error in the frame or MAXDATA at the host exceeding MAXDATA in the BARR/RJE configuration. Indicated by a V on the communication scope.
No reply received in time	Count of received timeouts. Whether Barr is a remote or host, the program expects to receive frames in a timely manner (usually within 3 seconds). Indicated by a T or N on the communication scope.
Aborted frames	Number of aborted frames received by BARR/RJE. Indicated by an A on the communication scope.
Frames received out of sequence	Number of SDLC information frames received with the wrong sequence number because a previous information frame probably had a CRC error. The out-of-sequence frames are discarded and the host is asked to retransmit the lost frame.
Checkpoint retransmissions	Number of times BARR/RJE started retransmission of SDLC information frames because a poll frame sent from the host did not acknowledge all previously sent frames. Probably a frame was received by the host with a CRC error.
Rej retransmissions	Number of times BARR/RJE started retransmission of SDLC information frames after a Rej frame was received from the host. Probably a frame was received by the host with a CRC error. Rej is used only in full-duplex SDLC.
Rej frames transmitted	Number of Rej frames sent. Rej is sent in full-duplex SDLC when an information frame is received out of sequence.
Rej frames received	Number of Rej frames received. Rej is sent in full-duplex SDLC when an information frame is rejected because it was received out of sequence.
Largest frame received	Size of the largest frame received. Comparing this value to the bind data will help to determine if the equipment between the host and BARR/RJE has been configured for a large enough frame size.

MS/LUA

If you have an MS/LUA connection, you will see the following link statistics.

Statistic	Description
Lines transmitted	Total number of data lines that the Send command or LAN connections read and BARR/RJE sends to a destination.
Lines punched or received	Number of data lines received on the host print or punch stream to the Barr computer.
Active SNA sessions	Number of SNA RJE sessions currently active, including printers, punches, readers, console, and commands from the keyboard.
Frames transmitted	Number of MS/LUA frames sent to the host.
Frames received without errors	Number of MS/LUA frames received without errors.
Frames received with errors	Number of MS/LUA frames received with either CRC errors or frames shorter than two bytes, indicated by an E on the communication scope.

Bind data

Bind data defines the operational rules for each partner LU. The bind data originates from the VTAM Logmode Table, the PU definition, and the RJE system. (For more information, see the Communication link parameters topic.) JES2 parameters override LOGMODE parameters for the bind data.

To view bind data, open the RJE Diagnostics utility. To display or hide the bind data, on the menu bar, select View | Bind Data.

Each bind data byte is assigned a number from 0 to 25. Bytes 14 through 25 of the bind data correspond to bytes 1 through 12 of the LOGMODE data’s PSERVIC parameter. For more information about the PSERVIC parameter, see the Logmode table entry topic. For more information about bind data, see the IBM publication: SNA Sessions between Logical Units.

The following table describes each byte displayed in the bind data.

Byte	Values	Description	LOGMODE
0	31	Bind command code
1	01	Activation code is non-negotiable
2	03	FM profile	FMPROF=X’03’
3	03	TS profile	TSPROF=X’03’
4	A3	Primary LU protocol; compression on receive	PRIPROT=X’A3’
	A1	Primary LU protocol; no compression on receive	PRIPROT=X’A1’
	B3	Primary LU protocol; compression on receive	PRIPROT=X’B3’
	B1	Primary LU protocol; no compression on receive	PRIPROT=X’B1’
5	A3	Secondary LU protocol; compression on send	SECPROT=X’A3’
	A1	Secondary LU protocol; no compression on send	SECPROT=X’A1’
	B3	Secondary LU protocol; compression on send	SECPROT=X’B3’
	B1	Secondary LU protocol; no compression on send	SECPROT=X’B1’
6	70	Common LU protocol	COMPROT=X’7080’
7	80	Common LU protocol	COMPROT=X’7080’
8	07	Barr to Controller pacing	SSNDPAC=7
9	07	Controller to Barr pacing; PACING=7	SRCVPAC=7
10	85	Input buffer size=256	RUSIZES=X’8585’
	86	Input buffer size=512	RUSIZES=X’8686’
	87	Input buffer size=1024	RUSIZES=X’8787’
	F3	Input buffer size=120	RUSIZES=X’F3F3’
	F4	Input buffer size=240	RUSIZES=X’F4F4’
	F5	Input buffer size=480	RUSIZES=X’F5F5’
	F6	Input buffer size=960	RUSIZES=X’F6F6’
11	85	Output buffer size=256
	86	Output buffer size=512
	87	Output buffer size=1024
	F3	Output buffer size=120
	F4	Output buffer size=240
	F5	Output buffer size=480
	F6	Output buffer size=960
12	07	Host RJE to Controller pacing; (LU)VPACING=7	PSNDPAC=7
13	07	Controller to Host RJE pacing; (APPL)VPACING=7
14	01	LU type 01	PSERVIC=X’01
15	10	FM header set 1	PSERVIC=X’0110
16	20	LU profile for PDIR (SETUPHDR)	PSERVIC=X’011020
	40	LU profile for compaction	PSERVIC=X’011040
	60	LU profile for compaction and PDIR (SETUPHDR)	PSERVIC=X’011060
17	00	Reserved	PSERVIC=X’01106000
18	91	SCS output; Full base +TRN +IRS	PSERVIC=X’0110600091
	F1	SCS output; FCBLOAD without SLD	PSERVIC=X’01106000F1
	F9	SCS output; FCBLOAD with SLD	PSERVIC=X’01106000F9
19	00	Not used	PSERVIC=X’01106000F900
20	C0	Output media – document and card files	PSERVIC=X’01106000F900C0
	E0	Output media – document, card, and exchange files*	PSERVIC=X’01106000F900E0
	20	Output media – exchange files*	PSERVIC=X’01106000F90020
	40	Output media – card (reader and punch) files	PSERVIC=X’01106000F90040
	80	Output media – document files	PSERVIC=X’01106000F90080
21	00,80	FM header flags	PSERVIC=X’01106000F9008000
22	00	Reserved	PSERVIC=X’01106000F900800000
23	01	SCS input includes TRN+IRS	PSERVIC=X’01106000F90080000001
24	00	Reserved	PSERVIC=X’01106000F9008000000100
25	40	Input media – card format	PSERVIC=X’01106000F900800000010040’

*Barr software does not support exchange media.

Interpreting RJE diagnostic data

RJE Diagnostics utility

What do you want to do?

See also:

Communication scope characters

Dial-Up scope characters

802.2 LLC2

802.2 examples

HPR/IP

HPR/IP examples

SDLC

SDLC examples

Dedicated line examples

Modulo 128

MS/LUA

Link statistics

802.2 LLC2 and HPR/IP

SDLC

MS/LUA

Bind data