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-24
WRITE Procedure
Continuation WRITE (Line in WRITE State)
All WRITEs following the initial one are continuation WRITEs. A continuation WRITE
(Example 3-7
) causes Envoy, on behalf of the application process, to send the message
in the application process’s buffer to the remote station. The call to the WRITE
procedure completes when the remote station acknowledges the message. The successful
transmission of a continuation message is indicated by a condition code of CCE upon
completion of the WRITE. Following the transmission of a continuation message, the
line is in the WRITE state.
The file-system errors shown in Table 3-13
can occur on a continuation WRITE.
171 No response to line bid. The line bid was attempted the
number of times specified by the retry value.
CONTROL
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
Example 3-7. Continuation WRITE (Line in WRITE State)
Local Remote
line state = WRITE
CALL WRITE(...)
|
| message 1 -->
|
| <-- ACK1
|
(WRITE completes)
error = 0
line state = WRITE
Table 3-12. Errors on Initial WRITE for BISYNC Point-to-Point (page 2 of 2)
Error
Number Description
Resultant Line
State