Installation guide

62 DC 900-1564A
Synchronous Link Control (SLC) Programmer’s Guide
5.1 Attach (All Access Modes)
Table 5–3 shows the DLI_ICP_CMD_ATTACH header format. See Section 4.1.1 on page 35
for a functional description. There is no associated data area.
a
Requirements for non-DLI calls: ICP Header fields must be in network byte-order, Protocol Head-
er fields must be in client byte order, and the ICP Header
usICPCount field is required.
b
The ICP requires that each DLI_ICP_CMD_ATTACH command written to the ICP declare the ICP node
number (3–126) through which the ICP is to send responses to the application. The DLI application pro-
gramming interface handles this automatically.
c
This returned Session ID must be provided on all subsequent writes for this link.
Table 5–3: DLI_ICP_CMD_ATTACH Header Format
Field Command Value (Write) Response Value (Read)
Freeway Header (network byte-order; used in DLI calls only):
usFWPacketType = FW_DATA = FW_DATA
usFWCommand = FW_ICP_WRITE = FW_ICP_READ
usFWStatus = 0 = 0
ICP Header
a
usICPClientID = 0 = 0
usICPServerID = 0 = 0
a
usICPCount = 16 (non-DLI calls only) = 16 (non-DLI calls only)
usICPCommand = DLI_ICP_CMD_ATTACH = DLI_ICP_CMD_ATTACH
iICPStatus = Client memory order
(Table 5–2 on page 61)
= DLI_ICP_CMD_STATUS_OK or
negative error code (slc_errs.h file)
usICPParms[0] = ICP return node
b
= ICP return node
usICPParms[1] = 0 = 0
usICPParms[2] = 0 = 0
Protocol Header
a
usProtCommand = DLI_ICP_CMD_ATTACH = DLI_ICP_CMD_ATTACH
iProtModifier = Access mode (Table 4–1 on page 33) = Access mode (Table 4–1 on page 33)
usProtLinkID = Link number = Link number
usProtCircuitID = 0 = 0
usProtSessionID = 0 = Session ID assigned by ICP
c
usProtSequence = 0 = 0
usProtXParms[0] = 0 = 0
usProtXParms[1] = 0 = 0