HP-UX SNAplus2 Upgrade Guide (August 2003)

Changes in SNAplus2 Functions in R6.0 and later releases

LUA Session Activation

Chapter 4 71

LUA Session Activation

The following features of LUA session activation have been changed:

• In SNAplus, if the LU speciﬁed on an LUA RUI_INIT verb is deﬁned

to use a host connection that is currently inactive and not “activate

on demand,” the verb waits for the connection to be started. In R6.0

and later releases, the verb returns with primary return code

LUA_UNSUCCESSFUL. The secondary return code is an SNA sense code

indicating that the host LS is inactive.

• In SNAplus, an LUA application could access only LUs that were

explicitly deﬁned for use with LUA (rather than for use with 3270

emulation or RJE). In R6.0 and later releases, the application can

specify any type 0–3 LU. This enables the use of 3270 emulation

programs that operate using LUA (such as the sample LUA

application provided with SNAplus2, or emulation programs that

may be provided by other vendors). You may need to check the LUs

used by LUA applications, to ensure that applications are accessing

the LUs intended for their use and not taking up LUs intended for

3270 emulation.

• When an R6.0 or later LUA application speciﬁes the name of an LU

in a pool, it accesses this LU if it is available, or any other available

LU in the pool if the named LU is not available. In SNAplus, the

application would access any free LU in the pool; SNAplus did not

attempt to select the named LU in preference to other LUs in the

pool.