Envoy Application Programming Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Application Programming With Envoy
- 7 ADM-2 Multipoint Supervisor Protocol
- 8 TINET Multipoint Supervisor Protocol
- 9 Burroughs Point-To-Point Protocol
- 10 Asynchronous Line Supervisor Protocol
- A ASCII Character Set
- B ASCII to EBCDIC Code Conversion
- C File-System Procedures
- D Statistics Messages
- E S-Series Changes to Envoy
- NonStop™ Himalaya S-Series Server Architecture
- G-Series Migration Considerations
- CBSENSEON and CFSENSEON Modifiers
- LEOTRESYN and NOLEOTRESYN Modifiers
- Treatment of Characters After the Termination Character
- Number of SYN Characters
- DTR Drop
- Reporting of Parity Error
- Half-Duplex Support for Asynchronous Lines
- Controller Replacement
- SYSGEN and COUP
- Unit Numbers
- FDX Line Changes
- No Support for Auto-Call Unit
- Glossary
- Index
Burroughs Point-To-Point Protocol
Envoy Application Programming Manual—427159-001
9-7
File-System Errors
File-System Errors
Upon completion of a file-system request, the Compaq application process should check
for the Guardian 90 file-system error codes listed in Table 9-6.
5u
6v
7w
Note. It is advisable to use message-block numbers as a standard practice; it is easier to write
an application program if the current message is identified at all times.
Table 9-6. File-System Errors for Burroughs Point-to-Point
Error Code Description
0 Operation successful
160 Request is invalid for device state; protocol error
161 Impossible event occurred for line state
162 Operation timed out
163 EOT received
165 RVI received
166 ENQ received
167 EOT received on line bid
168 NAK received on line bid
171 No response or invalid response received
172 Reply not proper for protocol
173 Maximum allowable NAKs received
177 Text overrun (insufficient buffer space for data transfer)
Table 9-5. Lowercase Letters for Block Number
Block Number bl#