HP-UX SNAplus2 R7 LUA Programmer's Guide

SLI Verbs
SLI_BID
lua_message_type
Message type of the received message, which is one of the following:
LUA_MESSAGE_TYPE_LU_DATA
LUA_MESSAGE_TYPE_SSCP_DATA
LUA_MESSAGE_TYPE_RSP
LUA_MESSAGE_TYPE_BID
LUA_MESSAGE_TYPE_BIND
LUA_MESSAGE_TYPE_BIS
LUA_MESSAGE_TYPE_CANCEL
LUA_MESSAGE_TYPE_CHASE
LUA_MESSAGE_TYPE_LUSTAT_LU
LUA_MESSAGE_TYPE_LUSTAT_SSCP
LUA_MESSAGE_TYPE_QC
LUA_MESSAGE_TYPE_QEC
LUA_MESSAGE_TYPE_RELQ
LUA_MESSAGE_TYPE_RTR
LUA_MESSAGE_TYPE_SBI
LUA_MESSAGE_TYPE_SIGNAL
LUA_MESSAGE_TYPE_STSN
The SLI uses the application’s LUA interface extension routines to receive and respond to the BIND and
STSN requests.
lua_flag2
One of the following flags will be set to
1 to indicate on which message flow the data was received:
lua_flag2.sscp_exp
lua_flag2.lu_exp
lua_flag2.sscp_norm
lua_flag2.lu_norm
lua_peek_data
The first 12 bytes of the message data (or all of the message data if it is shorter than 12 bytes)
If lua_rh.rri is off (request unit) and lua_rh.sdi is on (sense data included), this indicates that LUA has
converted a request unit sent by the host into an exception request (EXR). In this case, bytes 0–3of
lua_peek_data contain the sense data associated with the exception, and bytes 4–6 contain up to the first
3 bytes of the original request unit.
Successful Execution: Status Information
If the verb returned LUA status information instead of data, LUA returns the following parameters:
lua_prim_rc
LUA_STATUS
lua_sec_rc
LUA_READY
The SLI session is now ready to process additional commands. This status is used after a previous
LUA_NOT_READY status was reported, or after an SLI_CLOSE verb completed with lua_prim_rc set to
LUA_CANCELLED and lua_sec_rc set to RECEIVED_UNBIND_HOLD or RECEIVED_UNBIND_NORMAL.
107