Basic route data vector (X'000200010001')

The format of the basic route data vector is shown in Table 1. A basic route data vector will be built for each virtual route being collected on (excluding those that are reset, inactive, or pending active) per request for virtual route data. A virtual route is identified by destination subarea, virtual route number, and transmission priority.

Table 1. Basic route data vector
Byte	Type	Description
8–11	binary	Destination subarea
12	binary	Transmission priority
13	binary	Virtual route number
14–17	binary	Adjacent subarea
18	binary	Explicit Route Numbers Bit setting B'1111 ....' Initial explicit route number B'.... 1111' Actual explicit route number
19	binary	Reverse explicit route number
20–21	binary	Number of sessions on the virtual route
22	binary	Current minimum window size
23	binary	Current maximum window size
24	binary	Default minimum window size
25	binary	Default maximum window size
26–29	binary rolling counter	Number of times window size is reset to minimum
30–33	binary	Number of PIUs on the VR waiting to be sent
34	binary	Virtual route state: Hex value X'01' Inactive X'02' Pending inactive X'03' Flush in progress X'05' Active X'06' DACTVR FORCE in progress
35	binary	Flow control state Bit setting B'.... ..00' Route is blocked B'.... ..01' Route is held B'.... ..11' Route is open Bits not shown are reserved.
36–39	binary	Number of times that the virtual route was in the held state (not including current instance)
40–47	binary	Time that the virtual route has been in the held state if currently held
48–55	binary rolling counter	Total time that the virtual route was in the held state (not including current held time)
56–63	binary resettable	Maximum time that the virtual route was in the held state (not including current time) for any given held instance since last reset
64–71	binary resettable	Timestamp indicating when maximum held instance since last reset left the held state
72–75	binary rolling counter	Number of times the virtual route was blocked (not including current instance)
76–83	binary	Time that the virtual route has been in the blocked state if currently blocked
84–91	binary rolling counter	Total time that the virtual route was in the blocked state (not including current blocked time)
92–99	binary resettable	Maximum time that the virtual route was blocked (not including current time) for any given blocked instance since last reset
100–107	binary resettable	Timestamp indicating when maximum blocked instance since last reset left the blocked state
108–109	binary	TOTAL number of LU-LU sessions on the virtual route
110–111	binary	Current pacing request send count
112	binary	Current pacing window size
113–116	binary	Outbound PIU count over VR
117–120	binary	Inbound PIU count over VR