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
Software Concepts
Envoy Application Programming Manual—427159-001
2-13
Point-to-Point Operation
When a station has data to send, it bids for the line by calling the WRITE procedure.
The bid (that is, an ENQ) is automatically sent across the line when you issue a WRITE
while the controller is in the CONTROL state. For the bid to be successful, the remote
station must be monitoring the line with a call to the READ procedure.
If the receiver is monitoring the line, Envoy acknowledges the line bid, accepts the
transmission, deposits the received data in the application buffer, and returns an error
code of zero (operation successful). The transmission is not acknowledged until the
application issues a continuation READ. The initial WRITE by the transmitter that
causes a bid for the line also transmits the first message if the line bid is successful.
Subsequent calls to WRITE transmit messages but do not cause a bid for the line. The
end of transmission (EOT) is indicated by the transmitter when it calls the READ
procedure to again monitor the line.
If the receiver is not monitoring the line, the transmitter’s initial WRITE completes with
an error 171 (no response or invalid response received).
Example 2-4
shows the interaction between WRITE procedure calls in the transmitting
station and READ procedure calls in the receiving station.
Example 2-3. Monitor the Line for Incoming Messages
Receiver Receiver
CALL READ CALL READ
| |
| |
(READ completes) (READ completes)
error = 162 error = 162
Following the receipt of the "operation timed out" error, the
line state is CONTROL.