HP-UX SNAplus2 R7 LUA Programmer's Guide

SLI Verbs
SLI_SEND
between the SLI_BID and SLI_RECEIVE verbs. To ensure that it receives the same message that was identified in
the SLI_BID, it should set the lua_flag1 flags on SLI_RECEIVE to accept data only on the flow identified in the
SLI_BID response.
Pacing may be used on the primary-to-secondary half-session (this is specified in the host configuration), in order
to protect the LUA application from being flooded with messages. If the LUA application is slow to read messages,
SNAplus2 delays the sending of pacing responses to the host in order to slow it down.
5.6 SLI_SEND
The SLI_SEND verb sends an SNA request or response unit from the LUA application to the host, over either the
LU session or the SSCP session.
An application can have at most two SLI_SEND verbs outstanding at a time, which must be on different session
flows.
5.6.1 Supplied Parameters
The application supplies the following parameters:
lua_verb
LUA_VERB_SLI
lua_verb_length
The length in bytes of the LUA verb record.
Set this to sizeof(LUA_VERB_RECORD).
lua_opcode
LUA_OPCODE_SLI_SEND
lua_correlator
Optional. A four-byte value that you can use to correlate this verb with other processing within your
application. LUA does not use or change this information.
lua_luname
The name in ASCII of the LU used by the session. This must match the LU name of an active LUA session,
as returned on the SLI_OPEN verb.
This parameter is required only if the lua_sid parameter is 0 (zero). If a session ID is supplied in lua_sid,
LUA does not use this parameter.
This parameter must be eight bytes long; pad on the right with spaces, 0x20, if the name is shorter than
eight characters.
lua_sid
The session ID of the session. This must match a session ID returned on a previous SLI_OPEN verb.
This parameter is optional; if you do not specify the session ID, you must specify the LU name for the session
in the lua_luname parameter.
lua_data_length
The length of the supplied data.
137