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
TINET Multipoint Supervisor Protocol
Envoy Application Programming Manual—427159-001
8-23
WRITE Procedure
Table 8-7 lists the file-system errors that may occur on a READ.
WRITE Procedure
The WRITE procedure is used to select and transmit a message to a terminal
(Example 8-11
).
A WRITE (either a write-data or a write-tutorial-mask message) causes Envoy, on
behalf of the application process, to select the terminal indicated by the address-list
entry number in the message control word, bits 8:15 (the entry number is placed in the
message control word by the application process). Once the select address has been
issued, the message in the buffer of the application process is transmitted to the terminal.
The call to the WRITE procedure completes when the terminal acknowledges the
message with an EOT indication. The successful transmission of the message is
indicated by a condition code of CCE upon completion of the WRITE.
Table 8-7. READ File-System Errors
Error Numbers Description Resultant Line State
0 No error. A station responded with a message.
Message returned to the buffer of the applica-
tion process.
READ
160 Request is invalid for device state; protocol
error.
CONTROL
161 Impossible event occurred for line state CONTROL
171 No response received. The terminal indicated
in the message control word did not respond
to the poll sequence within the line’s timeout
period. The terminal is placed in the nonre-
sponding terminal list.
CONTROL.
172 Reply not proper for protocol. The data
received while waiting for a response to the
poll sequence was not proper for the TINET
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
176 Poll sequence ended with no responder. The
specified number of passes were made
through the poll list and no message was
received. This error may also indicate that an
empty poll list was specified.
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
178 No address list was specified. CONTROL