SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
4-4
SNAX/APC Object Types
SNAX/APC Object Types
The following object types are used by SNAX/APC. Note that not all of them are used
during the configuration.
PROCESS The PROCESS object type defines the SNAX/APC process. This
object type enables the operator to control SNAX/APC and its
subordinate objects. It is frequently used to obtain status
information, using SCF commands such as INFO, TRACE, and
STATUS. This object is created by using the RUN command in
TACL or the START SERVER command in PATHCOM.
An example object name would be $APC1.
LU This represents the local LU, the logical unit controlled by the
Tandem system.
An example object name would be $APC1.LU01.
PTNR-LU This represents the partner, or remote, LU. It is known as the
partner because this LU is a potential partner in a session with the
local LU. Similarly, it is also known as the remote LU because it
resides on a node other than that of the Tandem system. It is
sometimes also referred to as the target.
An example object name would be $APC1.LU01.CICSLU62.
PTNR-MODE This represents the set of definitions for a session type to be held
between local and remote LUs. The mode defines session
characteristics such as the default maximum number of sessions,
contention winners and losers, and pacing window sizes. There may
be more than one mode type defined.
An example object name would be
$APC1.LU01.CICSLU62.LU62BIND.
SESSION This represents an LU-LU session. This object is not created at
configuration time.
An example object name would be
$APC1.LU01.CICSLU62.LU62BIND.013A.
TPN This represents a local transaction program.
An example object name would be $APC1.LU01.ACCT.