OSI/TS Configuration and Management Manual

NonStop Kernel File-System Interface
OSI/TS Configuration and Management Manual—424831-001
7-37
Releasing a Transport Connection
Table 7-8 shows completion codes for READ and WRITEREAD calls during data
transfer.
Releasing a Transport Connection
You can use CONTROL 12, WRITE, or WRITEREAD procedure calls to request
a transport connection release. These procedures terminate the connection
between the transport entities. OSI/TS interprets any of these calls as a T-
DISCONNECT request service primitive. You must use a WRITE or a
WRITEREAD call if you want to include data in the release request. (Data
cannot be included when using a class 0 connection.)
CONTROL 12 Procedure
To use the CONTROL procedure, issue a call with the following syntax:
In class 0, OSI/TS sends an N-DISCONNECT request to the Network Layer. In
classes 1, 2, 3, and 4, OSI/TS sends a DR-TPDU to the remote peer and then
waits for a DC-TPDU. It sends an N-DISCONNECT to the Network Layer only
after it receives a DC-TPDU.
Table 7-7. WRITE Call Completion Codes During Data Transfer
Code Significance
0
Successful operation. count-written indicates number of octets
written, including MCW.
21
An illegal write-count is specified.
140 Connection does not exist or has been aborted. Issue
SETPARAM to fetch reason.
179 Invalid MCW specified.
Table 7-8. READ or WRITEREAD Call Completion Codes During Data
Transfer
Code Significance
0
Successful operation. count-written indicates number of octets
written, and read-count indicates number of octets returned. Both
include the MCW.
140 Connection does not exist or has been aborted. Issue
SETPARAM to fetch reason.
CALL CONTROL ( filenum, 12, [, tag ] );