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
Burroughs Point-To-Point Protocol
Envoy Application Programming Manual—427159-001
9-13
WRITE Procedure
Table 9-11 lists the file-system errors that may occur on an initial WRITE.
Table 9-11. Initial WRITE File-System Errors
Error
Number Description
Resultant
Line State
0 No error. Message was received and is in the buffer of the
application process.
WRITE
161 Impossible event occurred for line state. CONTROL
162 Operation timed out. No acknowledgment of the message was
received within the timeout limit. Envoy asked the remote for
an acknowledgment by sending an ENQ the number of times
specified by the retry limit.
CONTROL
163 EOT received. An EOT was received while waiting for the
line bid or for the message.
CONTROL
165 RVI received. The message was successfully transmitted to
the remote. The remote acknowledged the message by send-
ing DLE "<" ACK instead of just ACK. This is a polite
request to the local station to give up master status by send-
ing an EOT so that the remote station can transmit.
WRITE
166 ENQ received in response to line bid. The remote station is
also bidding for the line. If the local station is the primary,
then Envoy waited for the remote to accept the local station’s
line bid the number of times specified by the retry limit.
CONTROL
If the local station is the secondary, the application process
should call the READ procedure. This is a continuation
READ and causes Envoy to acknowledge the remote sta-
tion’s line bid and receive a message. The application process
can repeat its WRITE later.
READ
167 EOT received in response to line bid. CONTROL
168 NAK received in response to line bid. The remote station is
not ready to receive.
CONTROL
171 No bid received. No line bid was received within the timeout
and retry limits.
CONTROL
172 Reply not proper for protocol. The data received while wait-
ing for a line bid or for a message was not proper for the pro-
tocol.
CONTROL
173 Transmission error. Text was received with a character parity
error or a block-check character error. A NAK was sent, and
the message was retransmitted the number of times specified
by the retry value.
CONTROL
177 Text overrun. Either the data received while waiting for a line
bid exceeds three characters, or 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