HP-UX SNAplus2 R7 Administration Guide

Configuring APPC Communication
Defining Modes and Classes of Service
Name
The name of the mode you are defining. The mode name is a string of 1–8 characters.
APPC applications that use this mode, including both local and remote applications, may also use this name,
so check the name with your application developer (or refer to your product documentation for a third-party
application).
COS name
The name of the class of service for this mode. The name is a string of 1–8 characters. Usually you can
simply specify
#INTER for modes used for interactive data exchange and #BATCH for modes used for bulk
data transfer.
This field applies only to a network node.
If you do not know what value to specify, consult your SNA network planner.
Session limits
Use the following fields to specify session limits:
Initial session limit
The maximum number of sessions (up to the maximum session limit) that a pair of LUs can have using
this mode, unless a different maximum is negotiated using CNOS.
Normally, use the value 8 for this field. If you are in doubt, consult your SNA network planner or
APPC application developer (or for a third-party application, the product documentation).
Maximum session limit
The maximum number of sessions (up to 32,767) permitted between a pair of LUs using this mode,
even with CNOS negotiation.
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:
117