Envoy Application Programming Manual

Table Of Contents
Burroughs Point-To-Point Protocol
Envoy Application Programming Manual427159-001
9-14
WRITE Procedure
Continuation WRITE (Line in WRITE State)
All WRITEs following the initial one are continuation WRITEs. A continuation WRITE
(Example 9-5) causes Envoy, on behalf of the application process, to send the message
in the buffer of the application process 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 transmission of a continuation message, the line is
in the WRITE state.
Table 9-12
lists the file-system errors that may occur on a continuation WRITE.
Example 9-5. Continuation WRITE
Local Remote
line state = WRITE
CALL WRITE(...)
message -->
<-- ACK
(WRITE completes)
error = 0
line state = WRITE
Table 9-12. Continuation WRITE File-System Errors (page 1 of 2)
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 num-
ber 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 the remote station can transmit.
WRITE
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