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-19
READ Procedure
Continuation READ (Line in READ State)
All READs following the initial one are continuation READs. A continuation READ
(Example 3-3) causes Envoy, on behalf of the application process, to send the proper
acknowledgment for the preceding message, read the next message, and return the
message to the buffer of the application process. The successful receipt of a message is
indicated by a condition code of CCE upon completion of the READ. Following the
receipt of a message, the line is in the READ state.
162 Operation timed out. A line bid was not received within the
timeout and retry.
CONTROL
163 EOT received. An EOT was received while waiting for the
line bid.
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
170 No ID sequence received during circuit assurance mode. DISCONNECT
172 Reply not proper for protocol. The data received while
waiting for a line bid or for text was not proper for the
BISYNC protocol.
CONTROL
173 Transmission error. The message received was in error and a
NAK sequence was sent the number of times specified by the
retry value.
CONTROL
177 Text overrun. The length of the message received exceeds the
length specified in the read count parameter. The READ was
attempted the number of times specified by the retry value.
CONTROL
Table 3-10. Errors on Initial READ for BISYNC Point-to-Point (page 2 of 2)
Error
Number Description
Resultant Line
State