HP-UX SNAplus2 R7 LUA Programmer's Guide

SLI Verbs
SLI_CLOSE
This value is the operating system return code. Check your operating system documentation for the meaning
of this return code.
5.1.3 Interaction with Other Verbs
The SLI_OPEN verb must complete successfully before this verb can be issued.
Only one SLI_BID for each session can be outstanding at any one time.
After the SLI_BID verb has completed successfully, it may be re-issued by setting the
lua_flag1.bid_enable parameter
on a subsequent SLI_RECEIVE verb. If the verb is to be re-issued in this way, the application program must not
free or modify the storage associated with the SLI_BID verb record.
If a message arrives from the host when an SLI_RECEIVE and an SLI_BID are both outstanding, the SLI_RECEIVE
completes and the SLI_BID is left in progress.
5.1.4 Usage and Restrictions
Each message that arrives will only be bid once. Once an SLI_BID verb has indicated that data is waiting on a
particular session flow, the application should issue the SLI_RECEIVE verb to receive the data. Any subsequent
SLI_BID will not report data arriving on that session flow until the message which was bid has been accepted by
issuing an SLI_RECEIVE verb.
If there is data available on more than one session flow, the data on the highest-priority flow will be returned to the
application. The flow priorities are as follows (highest to lowest):
• SSCP expedited
• LU expedited
• SSCP normal
• LU normal
Once a message has been read using the SLI_RECEIVE verb, it is removed from the incoming message queue,
and cannot be accessed again. The application can use SLI_BID as a non-destructive read to check the type of
data available and determine how to process it, and then issue a subsequent SLI_RECEIVE to collect the data.
However, if it issues the SLI_RECEIVE with multiple lua_flag1 flags set to accept data on more than one flow, it
may receive a different message from the one identified in the SLI_BID, if data arrived on a higher-priority flow
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.
The lua_data_length parameter indicates the length of data in lua_peek_data. If this is less than 12, indicating that
the waiting message is shorter than 12 bytes, the remaining bytes in lua_peek_data are undefined and the application
should not attempt to examine them.
5.2 SLI_CLOSE
The SLI_CLOSE verb ends both the LU session and the SSCP session for a given LU.
5.2.1 Supplied Parameters
The application supplies the following parameters:
lua_verb
111