HP-UX SNAplus2 R7 LUA Programmer's Guide

RUI Verbs
RUI_WRITE
If the application specified the lua_luname parameter when issuing this verb, rather than specifying the session
ID, LUA supplies the session ID.
lua_th
The completed TH of the message written, including the fields filled in by LUA. You may need to save the
value of lua_th.snf (the sequence number) for correlation with responses from the host.
lua_rh
The completed RH of the message written, including the fields filled in by LUA.
lua_flag2
parameters
One of the following flags will be set to
1
to indicate which message flow the data was sent on:
lua_flag2.lu_exp
lua_flag2.sscp_norm
lua_flag2.lu_norm
The SNAplus2 implementation of LUA does not allow applications to send data on the SSCP expedited flow,
and so will never set the sscp_exp flag (although other LUA implementations may set it).
Unsuccessful Execution
If a verb does not complete successfully, LUA returns a primary return code to indicate the type of error and a
secondary return code to provide specific details about the reason for unsuccessful execution.
Verb Canceled
The following return codes indicate that the verb did not complete successfully because it was canceled by another
verb:
lua_prim_rc
LUA_CANCELLED
lua_sec_rc
LUA_TERMINATED
The verb was canceled because an RUI_TERM verb was issued for this session.
Parameter Check
The following return codes indicate that the verb did not complete successfully because a supplied parameter was
in error:
lua_prim_rc
LUA_PARAMETER_CHECK
lua_sec_rc
Possible values are:
LUA_BAD_DATA_PTR
The lua_data_ptr parameter contained a value that was not valid.
LUA_BAD_SESSION_ID
The lua_sid parameter did not match the session ID of any active LUA LU session.
LUA_DUPLICATE_WRITE_FLOW
An RUI_WRITE was already outstanding for the session flow specified on this verb (the session flow
is specified by setting one of the lua_flag1 flow flags to
1). Only one RUI_WRITE at a time can be
outstanding on each session flow.
LUA_INVALID_FLOW
101