HP-UX SNAplus2 Upgrade Guide (June 2003)

Changes in SNAplus2 Functions in R6.0 and later releases
APPC LUs, Modes, and Sessions
Chapter 4 67
APPC LUs, Modes, and Sessions
The following features of APPC configuration and management have
been changed.
• Instead of requiring implicit modes to be defined for each
LU-LU-mode combination, an SNAplus2 node now has a single
default mode defined, which is used if an application specifies an
unrecognized mode name. You do not need to define an implicit mode
for each LU-LU-mode combination, because SNAplus2 no longer
requires LU-LU-mode combinations to be defined before
communications can be established.
• Implicit partner LUsno longer need to bedefined, because SNAplus2
no longer requires LU-LU-mode combinations to be defined before
communications can be established.
• Mode definitions now specify a single maximum RU size (which can
be negotiated with the partner LU). There is no facility for specifying
the minimum acceptable RU size or for specifying different
maximum sizes for sending and receiving.
• The priority (high or low) of a mode is now specified in the definition
of the class of service (COS) it uses, rather than being specified
explicitly in the mode definition.
• There is no facility for specifying the partner LU's minimum
contention winner session limit. This parameter is defined in the
configuration of the partner LU at the remote system, and is not
required in the local SNAplus2 configuration.
• There is no longer a requirement for specifying the send pacing
count. In Release 6, sessions normally use adaptive pacing, which
does not require a fixed pacing count. The pacing count is required
only when communicating with a partner system that does not
support adaptive pacing; in this case, the receive pacing count
defined in the partner system's configuration is used.
• In SNAplus, sessions using a particular mode may be activated
automatically when the connection associated with that mode is
started, so that they will already be active when an application
attempts to use the mode. In Release 6, the mode is not associated
with a specific LS, and so the sessions are not activated until an
application first attempts to use the mode. If you need to activate