SNAX/APC Configuration and Management Manual

SNAX/APC Configuration and Management Manual—138787
2-1
2
Planning for SNAX/APC
This section provides instructions on how to plan the use and configuration of
SNAX/APC. Actual configuration examples are given in Section 4, Configuring
Network Resources for SNAX/APC, of this manual. This section contains five main
subsections:
•
LU 6.2 Data Structures. Before you can configure SNAX/APC, you must have an
appreciation of how the structures and processes inside a type 6.2 LU work together
to enable transaction program (TP) conversations. At the very minimum, you
should understand the relationships between local transaction programs controlled
by the local LU, the partner LUs, and their subordinate modes. Tandem has
extended the LU 6.2 standards of data structures to enable optional dynamic
configuration of partner LUs and their modes.
•
Tandem Access Method Configuration. Before installing SNAX/APC, you should
select the appropriate Tandem access method. This subsection reviews the access
method options.
•
IBM Configuration. The target LU (the other end of the conversation) must also be
configured to initiate and receive LU 6.2 traffic. The target LU could be in IBM’s
CICS on a mainframe, or an IBM AS/400, or a PC with APPC/PC. This subsection
reviews some of the requirements, but you must refer to the appropriate IBM
documentation for more detailed information.
•
Conversation-Level Security Considerations. Before you can implement
conversation-level security in SNAX/APC, you should understand the available
options and plan your configuration based on the options you choose. This
subsection explains how conversation-level security is implemented and how it is
controlled by configuration.
•
Sync Point Support Considerations. Before you can implement sync point in
SNAX/APC, you must be licensed to use sync point and you must provide the
majority of the sync point structure and functionality. The requirements are
discussed in the SNAX/APC Application Programming Manual. This subsection
explains how sync point support is controlled by licensing and configuration.
LU 6.2 Data Structures
The 6.2 type of LU maintains data structures representing the state and configuration of
its resources.
One set of these structures, called static, represents the LU-accessed network resources.
These static structures, depicted in Figure 2-1
, describe the characteristics of the LU, the
transaction programs that the LU can run, the partner LUs with which the LU can
communicate, and the modes characterizing possible sessions with particular partner
LUs.
Other data structure elements represent the dynamic environment created by the LU.
The main components, shown in Figure 2-2
, are transaction program instances in
execution (represented as transaction-program processes), active sessions with other