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

Chapter 4 103
APPC Subsystem Configuration
Planning APPC Configuration
Session Types for Different Remote LUs
You must configure at least one session type for each remote LU with
which the APPC subsystem will communicate.
A session type that will communicate with an independent LU on the
remote system must be an independent LU session type. An
independent LU on the HP 3000 can conduct multiple, simultaneous
APPC sessions with an independent remote LU. One local independent
LU can be configured to communicate with several remote LUs
simultaneously, as long as the remote LUs are all connected to the
HP 3000 through the same copy of SNA/SDLC Link/XL.
Session types that will communicate with dependent LUs on the host
must be dependent LU session types.
Session Types for Reserved Sessions
A group of users or an LU 6.2 product requiring guaranteed session
access should have one or more session types reserved for its use. When
you configure a reserved session type, you should specify LUs that no
other session type will use.
Planning the Number of Active Sessions
Every conversation between transaction programs requires an APPC
session. When planning the number of active sessions, you must take
into account the following restrictions:
1. The total number of simultaneously active sessions, for all session
types combined, may not exceed 256. You can configure more than
256 sessions, as long as you never have more than 256 sessions
active at once.
2. An independent LU session type has only one independent LU
associated with it. This independent LU can support a maximum of
256 active sessions.
3. A dependent LU session type can support up to 32 active sessions.
You must configure at least one dependent LU for every active
dependent LU session.
The number of sessions you will need for each session type depends on 3
things:
1. How many transaction programs will use the session type at once.
2. How many instances of each transaction program will be running at
once.
3. How many conversations each instance of a transaction program will
be conducting at once.