z/OS Communications Server: SNA Customization
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


RTP data vector (X'000300010001')

z/OS Communications Server: SNA Customization
SC27-3666-00

The format of the RTP data vector is shown in Table 1. RTP data vectors are built for each RTP specified in a collect request.

Table 1. RTP data vector
Byte Type Description
8–9 binary First byte
Bit setting
B'0000 0000'
Normal collect
B'1000 0000'
Exit called due to HPR path switch
B'0100 0000'
Exit called because RTP is being deleted
B'0010 0000'
Exit called due to HPR path switch with CP name change. The New remote network ID field and the New remote CP name field are set.

Second byte is reserved.

10–17 binary Local NCE
18–25 binary Local TCID
26–33 binary Rapid Transport Protocol (RTP) Physical Unit
34–41 EBCDIC Remote network ID
42–49 EBCDIC Remote CP name
50–57 EBCDIC New Remote network ID
58–65 EBCDIC New remote CP name
66–73 binary Remote NCE
74–81 binary Remote TCID
82 binary RTP state
83–86 binary HPR path switch timer
87–90 binary Round-trip delay
91–94

binary
rolling counter

Number of bytes sent over the RTP
95–98

binary
rolling counter

Number of bytes received over the RTP
99–102

binary
rolling counter

Number of PIUs that were first in segment sent over the RTP
103–106

binary
rolling counter

Number of PIUs that were middle in segment sent over the RTP
107–110

binary
rolling counter

Number of PIUs that were last in segment sent over the RTP
111–114

binary
rolling counter

Number of PIUs that were not segmented sent over the RTP
115–118

binary
rolling counter

Number of PIUs that were first in segment received over the RTP
119–122

binary
rolling counter

Number of PIUs that were middle in segment received over the RTP
123–126

binary
rolling counter

Number of PIUs that were last in segment received over the RTP
127–130

binary
rolling counter

Number of PIUs that were not segmented received over the RTP
131–134

binary
rolling counter

Number of times the allowed send rate changed
135–136

binary
rolling counter

HPR path switch attempts initiated by other RTP endpoint
137–138

binary
rolling counter

Total number of HPR path switch attempts initiated by this VTAM®
139–140

binary
rolling counter

HPR path switch attempts due to operator or VTAM command.

Path switch attempts due to any other failure (such as link failure or node failure) can be calculated by subtracting this value from the total number of path switch attempts.

141–142

binary
rolling counter

Total number of unsuccessful route selection attempts initiated by this VTAM during HPR path switch
143–144

binary
rolling counter

Unsuccessful HPR path switch due to operator command.

The number of unsuccessful path switches that originated due to any other failure (such as link failure or node failure) can be calculated by subtracting this value from the total number of unsuccessful path switch attempts.

145–148 binary Number of active LU-LU sessions using the RTP
149–152

binary
rolling counter

Amount of time in seconds that back pressure has been applied
153–154

binary
rolling counter

Total number of times that back pressure has been applied
155–156

binary
rolling counter

Number of times that back pressure has been applied due to HPR path switch
157–158

binary
rolling counter

Number of times that back pressure has been applied due queue depth exceeded.

The number of times that back pressure has been applied due to storage shortage can be calculated by subtracting the above two counts from the total count.

159–162

binary
rolling counter

Number of retransmitted NLPs
163–166

binary
rolling counter

Current number of unacknowledged buffers

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014