User`s guide

F: BSC Detailed Command and Response Formats
DC 900-1340I 245
The usICPCommand field of the ICP Header is DLI_ICP_CMD_WRITE. See Table F–11 on
page 256.
The client application is normally implemented to allow asynchronous receipt of both
the acknowledgment to these commands, which is
DLI_PROT_RESP_LOCAL_ACK (see
Table F–11 on page 256), and receipt of data received at the data link (see Table F–12 on
page 257).
For both messages, the usICPCommand field of the received ICP Header is
DLI_ICP_CMD_READ.
There are other protocol commands (and subsequent responses) that can be sent to or
received from the ICP (the general format is shown in Ta ble F– 7 on page 252 and
Table F–9 on page 254).
F.1.6 Link Disabling (Unbind)
When the client application is ready to terminate data transfer of a link, it processes a
DLI_ICP_CMD_UNBIND command and subsequent response to the ICP to disable the speci-
fied link. See Table F –5 on page 250.
F.1.7 Session Detach
When the client application is ready to terminate processing, it processes a
DLI_ICP_CMD_DETACH command and subsequent response for each node and link that is be
detached from session management. See Table F–3 on page 248.
After a session and link have been detached, the same, or another client application is
free to attach a session to the link. Without normal session detaches, any link that is
attached on the ICP is not re-usable, and the ICP must be re-downloaded to make the
link again available.
Roger
LaFrance —
The
underlined
appears to
contradict
Table F-11 on
page 260?