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
BISYNC Point-To-Point Protocol
Envoy Application Programming Manual—427159-001
3-20
READ Procedure
The file-system errors shown in Table 3-11 can occur on a continuation READ.
Example 3-3. Continuation READ (Line in READ State)
Local Remote
line state = READ
CALL READ(...)
|
| ACKn -->
| <-- message n
(READ completes)
error = 0
line state = READ
CALL READ (...)
|
| ACKn -->
| <-- EOT
(READ completes)
error \ 163
line state = CONTROL
Table 3-11. Errors on Continuation READ for BISYNC Point-to-
Point (page 1 of 2)
Error
Number Description
Resultant Line
State
0 No error. Message is returned to buffer of the application
process.
READ
140 Modem error. READ
160 Request is invalid for device state; protocol error. unknown
161 Impossible event occurred for line state. unknown
162 Operation timed out. The acknowledgment was sent but no
message was received within the timeout and retry limits.
CONTROL
163 EOT received. CONTROL
164 For switched lines, the disconnect sequence (DLE EOT) was
received. Data terminal ready is cleared.
DISCONNECT
For nonswitched lines, the disconnect sequence (DLE EOT)
was received.
CONTROL