HP-UX SNAplus2 R7 LUA Programmer's Guide

RUI Verbs

RUI_READ

The node was either not started or not conﬁgured properly for LUA applications. Check the SNAplus2

LUA conﬁguration parameters and start the node before running your application.

4.4.3 Interaction with Other Verbs

This verb can only be used when an RUI_READ has been issued and is pending completion (that is, the primary

return code is

IN_PROGRESS).

4.5 RUI_READ

The RUI_READ verb receives data or status information sent from the host to the application’s LU.

You can specify a particular message ﬂow (LU normal, LU expedited, SSCP normal, or SSCP expedited) from

which to read data, or you can specify more than one message ﬂow. You can have multiple RUI_READ verbs

outstanding, provided that no two of them specify the same ﬂow.

4.5.1 Supplied Parameters

The application supplies the following parameters:

lua_verb

LUA_VERB_RUI

lua_verb_length

The length in bytes of the LUA verb record.

Set this to sizeof(LUA_COMMON).

lua_opcode

LUA_OPCODE_RUI_READ

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 RUI_INIT or RUI_INIT_PRIMARY 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 RUI_INIT or

RUI_INIT_PRIMARY 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_max_length

The length of the buffer supplied to receive the data.