Use the SETAPPC LUADD command to define a local APPC/MVS LU to the APPC configuration.
Each LU managed by APPC/MVS must be defined by either an LUADD statement previously invoked through the SET APPC command or through the SETAPPC command. When an installation uses the ASCH transaction scheduler exclusively, only one LU is required. If other transaction schedulers are used, each scheduler requires a separate LU. An installation might choose to define additional LUs to isolate TPs for security or testing.
An installation can also define LUs that are not associated with transaction schedulers. These LUs handle work that is processed by APPC/MVS servers, rather than scheduled by a transaction scheduler. Such LUs are indicated by using the NOSCHED keyword on LUADD. Installations can also use NOSCHED LUs when they want to flow outbound allocate requests without having a transaction scheduler active. (Note that APPC/MVS servers can also run under LUs that are associated with transaction schedulers.)
You can modify an LU by overriding previously defined LUs made through either the SET APPC or SETAPPC commands. In this case, the SETAPPC LUADD command specifies an ACBNAME that names an existing LU and then the parameters to be modified. The only parameters you cannot modify with an overriding LUADD are the SCHED, NOSCHED, ALTLU, USERVAR, GRNAME, NQN and NONQN parameters. To change these parameters, first delete the LU with a SETAPPC LUDEL command and then issue a SETAPPC LUADD command to re-add the LU with a changes to the parameters.
Example:
SETAPPC LUADD,ACBNAME=MVSLU01,SCHED=ASCH,TPDATA=(SYS1.APPCTP),TPLEVEL=USERValue Range: A one- to eight-byte character string of uppercase letters A through Z, numerals 0-9, national characters (@,$,#) that must begin with an alphabetic or national character.
The SNA LU 6.2 architecture defines a network-qualified LU name to be up to 17 bytes in length and in the form network_id.network_LU_name, where network_id is the optional 8-byte id of the network and network_LU_name is the 8-byte local LU name. SAA CPI Communications allows the full 17-byte network-qualified LU name. However, for the ACBNAME keyword, specify only the 8-byte local LU name.
Default: None, this parameter is required.
SCHED indicates that the LU is associated with a transaction scheduler. schedname must match the name the transaction scheduler specifies when it calls the Identify service. For more information about the Identify service and its scheduler_name parameter, see z/OS MVS System Messages, Vol 3 (ASB-BPX).
NOSCHED indicates that the LU is not to be associated with a scheduler. When NOSCHED is specified, the LU becomes active as soon as APPC/MVS becomes active. Installations can use NOSCHED LUs to isolate work from schedulers when the work is to be processed by APPC/MVS servers. Installations can also use NOSCHED LUs to flow outbound allocate requests without having a transaction scheduler active.
Value Range: For schedname, the value is a one- to eight-byte character string and each character must be an uppercase letter (A-Z) or a numeral (0-9).
Default: When you omit both SCHED(schedname) and NOSCHED, the default is SCHED(ASCH).
When a NOSCHED LU is defined with the BASE option, the LU becomes the system base LU. That means the LU is to be the default LU used for outbound allocate requests from MVS™ programs, such as batch jobs, TSO/E users, started tasks, and other work requests that attempt to enter the network without being associated with a scheduler or an LU.
SETAPPC LUADD,ACBNAME=MVSLU02,NOSCHED,BASE,TPDATA=(SYS1.APPCTEST),TPLEVEL=SYSTEMIf you do not define a NOSCHED LU as a base LU, the base LU defined for the APPC/MVS transaction scheduler (ASCH) becomes the system base LU. If the system base LU does not exist , APPC/MVS rejects conversations allocated by MVS programs that are not associated with a scheduler or an LU.
IBM® recommends that you define one LU per transaction scheduler as the base LU for the scheduler. In addition, define a NOSCHED LU as the system base LU if you want to allow outbound requests from the system when no transaction schedulers are active.
When more than one LU is defined as the base LU, the one most recently defined is the base.
When you specify a valid value other than NONE, the LU's sessions persist when the APPC address space is canceled, forced, terminated, or automatically restarted. The sessions also persist during interruptions in scheduler service.
Any conversations that were active at the time of the interruption are lost. When APPC service is resumed, the conversation partners can re-establish these conversations, if desired.
Sessions do not persist in the event the LU is deleted.
Default: NONE
Value Range: Up to 44 characters in length consisting of one- to eight-byte character string of uppercase letters A through Z, numerals 0-9, national characters (@,$,#) that must begin with an alphabetic or national character.
Default: SYS1.APPCTP
Each TP can have different levels of TP profiles with scheduling characteristics associated with a user, a group of users, or all users (system). The TPLEVEL parameter tells the LU which of those levels of TP profile to search.
Value Range:
SYSTEM means that the LU searches for system-level TP profiles only (NOT for a specific user or group of users).
GROUP means that the LU searches for TP profiles associated with (1) a specific group of users and (2) system-level TP profiles, in that order.
USER means that the LU searches for TP profiles associated with (1) a specific user, (2) a group of users, and (3) system-level TP profiles, in that order.
Default: SYSTEM
If specified, the data is passed to the APPC XCF group member at the activation and deactivation of the associated LU. For information about the APPC XCF group, see z/OS MVS System Messages, Vol 3 (ASB-BPX).
Value Range: A one- to eight-byte character string of uppercase letters A through Z, numerics 0-9, or national characters (@, $, #), with the exception that the first character cannot be numeric (0-9).
Default: None
If specified, the data is passed to the APPC XCF group member at the activation and deactivation of the associated LU. For information about the APPC XCF group, see z/OS MVS System Messages, Vol 3 (ASB-BPX).
Value Range: A one- to eight-byte character string of uppercase letters A through Z, numerics 0-9, or national characters (@, $, #), with the exception that the first character cannot be numeric (0-9).
Default: None
See z/OS MVS Planning: APPC/MVS Management for advice and restrictions about selecting a generic resource name, and deciding which LUs should become members of a generic resource group.
Value Range: A one- to eight-byte character string of uppercase letters A through Z, numerals 0-9, national characters (@, $, #) and must begin with an alphabetic or national character.
Default: None. If the GRNAME parameter is not specified, the LU is activated but is not part of a generic resource group.
See z/OS MVS Planning: APPC/MVS Management for the requirements for enabling APPC/MVS LUs to support network-qualified names.
Default: NONQN
Value Range: A one- to eight-byte character string of uppercase letters A through Z, numerals 0-9, national characters (@,$,#) and must begin with an alphabetic or national character.
For an explanation of why SAA CPI partner LU names can be 17 characters, see the note under the ACBNAME parameter in ACBNAME(luname) .
Default: None; this parameter is required.
Default: NOPERSIST
Value Range: Up to 44 characters in length consisting of one- to eight-byte character string of uppercase letters A through Z, numerals 0-9, national characters (@,$,#) and must begin with an alphabetic or national character.
Default: SYS1.APPCSI