APPC Subsystem on MPE/XL Node Manager's Guide (30294-90007)

90 Chapter4
APPC Subsystem Configuration
Configuring the APPC Subsystem
Automatically Activated Sessions
Required. The number of sessions that will be
activated automatically when the APPCCONTROL
START command is issued or the APPCStart intrinsic
is called. The Automatically Activated Sessions
value must be less than or equal to the value in the
Maximum Number of Sessions field. The sum of the
Automatically Activated Sessions for all the
session types on the APPC subsystem must not exceed
256.
Default: 0
Unsolicited Binds
Required. Enables or disables unsolicited BINDs from
the remote LU. Enter Y or N. Hewlett-Packard
recommends that you disable unsolicited BINDs.
Y The remote LU will initiate all APPC
sessions by sending unsolicited BINDs
to the local LU. The HP 3000 will wait
for a BIND rather than sending an
INIT_SELF request to solicit a BIND.
The IBM host must be specifically
configured to send unsolicited BINDs.
N The local LU will initiate all APPC
sessions by sending INIT_SELF
requests to the host. The host will send
a BIND only in response to an
INIT_SELF request.
Default: N (unsolicited BINDs disabled)
APPC: Dependent LU List Data Screen
The “APPC: Dependent LU List Data” screen, shown in Figure 4-10, is
where you list the dependent LUs that are associated with a dependent
LU session type. You get to it from the “APPC: Dependent LU Session
Type Data” screen by pressing
[f1] (Go To LULIST).
The Path field of the “APPC: Dependent LU List Data” screen gives the
name of the dependent LU session type to which the LUs in the list
belong.
You can configure a maximum of 32 LUs for a dependent LU session
type. The number of LUs you configure must be greater than or equal to
the Maximum Number of Sessions value in the “APPC: Dependent LU
Session Type Data” screen.