Table of Contents
Advertisement
This field is usually set to the same value as the initial
session limit. If you are in doubt, consult your SNA
network planner or APPC application developer (or for
a third-party application, the product documentation).
Minimum contention winner sessions
The number of sessions (up to the session limit) that
SNAplus2 must reserve for use by the local LU as the
contention winner.
This field can usually safely be set to 0, but if you are
not sure, consult your SNA network planner.
The sum of the minimum contention winner sessions
and the minimum contention loser sessions must not
exceed the initial session limit.
Minimum contention loser sessions
The minimum number of sessions that SNAplus2 must
reserve for use by the local LU as the contention loser.
Together with the value in the Minimum contention
winner sessions field, this value determines how to
resolve contention for a session.
This can usually safely be set to 0, but if you are not
sure, consult your SNA network planner.
The sum of the minimum contention winner sessions
and the minimum contention loser sessions must not
exceed the initial session limit.
Auto-activated sessions
The number of sessions (up to the minimum contention
winner count) that are automatically activated after
CNOS negotiation has taken place for a session
between a local LU and partner LU using this mode.
Specifying a value for this field enables an LU that
uses this mode to start sessions automatically in
response to a request from a TP for a conversation to be
allocated immediately.
Receive pacing window
Use these fields to specify how many RUs can be
received before an SNA pacing response is sent:
Initial window size
Chapter 7
Configuring APPC Communication
Defining Modes and Classes of Service
197
Advertisement
Table of Contents
