Interpreting RJE diagnostic data

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?

See also:

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.

Dial-Up scope characters

To follow 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 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.

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

HPR/IP

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

HPR/IP examples

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.

MS/LUA

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

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.

MS/LUA

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.

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’

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.

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.

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

Statistic	Description
Lines transmitted	Total number of data lines that the Send command or LAN connections read and 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.