Adding a Local LU — LUADD Statement

The LUADD statement defines a local APPC/MVS LU that is to be added to the APPC configuration. Each LU on MVS must be defined with an LUADD statement that specifies a name for the LU, through the ACBNAME parameter. Other LUADD statement parameters are:

SCHED(name) or NOSCHED: Indicates whether the LU is associated with a transaction scheduler
BASE: Specifies whether the LU is a base LU
PSTIMER: Indicates the length of time that the sessions persist
TPDATA(name): Identifies the TP profile file associated with the LU
TPLEVEL(level): Identifies the level of TP for which the LU searches
ALTLU and USERVAR: Pass optional, installation-supplied data to an alternate transaction scheduler
GRNAME(genericname): Specifies a VTAM® generic resource name to be associated with the LU
NQN or NONQN: Specifies whether the LU is enabled to use a network-qualified partner LU name when first allocating an outbound conversation.

When an installation uses the APPC/MVS transaction scheduler exclusively, only one LU is required. If other transaction schedulers are used, each scheduler requires a separate LU. An installation might also choose to define additional LUs for use with APPC/MVS servers, or to isolate TPs for security or testing.