Table 1. Translate reply
request (TR-REPLY) request unit format| Byte |
Bit |
Value |
Description |
| 0 |
|
X'3F' |
Network services, access method RU |
| 1 |
|
X'08' |
Management services |
| 2 |
|
X'16' |
Request code |
| 3–4 |
|
|
Reserved |
| 5–6 |
0–3 |
|
Reserved |
| |
4–15 |
|
Procedure relation identifier (PRID) |
| 7 |
0 |
0 |
Unsolicited request |
| |
|
1 |
Solicited request |
| |
1 |
0 |
Last request |
| |
|
1 |
Not last request |
| |
2–7 |
|
Reserved |
| 8–9 |
|
|
Count of translate-reply requests |
| 10–13 |
|
|
Sense code |
| 14–n |
|
|
Translate reply data ¹ |
Note: - Bytes 14–n represent each byte in this Translate-Reply
Data table.
|
Table 2 represents
one translate inquiry data record. This record, and possibly additional
records, are contained in bytes 14–n of the Translate-Inquiry Request
(see Table 1).
The total number of records is equal to the count value shown in bytes
8–9 of Table 1.
Table 2. Translate reply
data| Byte |
Description |
| 0 |
Length of reply data |
| 1 |
Reply name characteristics |
| 1 |
Reserved |
| 2 |
Class of input name |
| 3 |
Input name type code |
| 4 |
Length of input name (maximum 8) |
| 5 |
Input name to be translated |
Table 3. Network identifier
1| Byte |
Description |
| 0 |
Network ID type code (X'FE') |
| 1 |
Length of network ID |
| 2 |
Network ID |
Table 4. Network identifier
2| Byte |
Description |
| 0 |
Network ID type code (X'FE') |
| 1 |
Length of network ID (maximum 8) |
| 2 |
Network ID |
Table 5. Translated name
data| Byte |
Description |
| 0 |
Sense code for this reply |
| 4 |
Translated name type code (maximum 8) |
| 5 |
Length of translated name |
| 6 |
Translated name |