SNAX/APC Configuration and Management Manual

Planning for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
2-6
SNAX/CDF Configuration
•
Remote PU objects. These represent adjacent nodes. At least one PU per line using
type 2.1 capabilities is required.
SNAX/CDF Configuration
There are no added requirements for configuration in order to use SNAX/APC with
SNAX/CDF. SNAX/CDF does not support parallel sessions. SNAX/CDF supports
dynamic configuration of the partner LU and partner mode, but a line must be pre-
defined to the remote PU.
EnvoyACP/XF SDLC Line Configuration
In order to run SNAX/APC using SNAX/CDF, you need to define at least one
EnvoyACP/XF SDLC line. For more information on SNAX/CDF configuration, see the
SNAX/CDF Configuration and Control Manual.
IBM Configuration
The SNAX/XF Configuration and Control Manual and the SNAX/APN Configuration and
Control Manual (K or S-series) contain some ideas on planning for connectivity in
APPN and subarea networks, but you are advised to consult IBM documentation for
details on actual configuration. The following text presents some examples for your
consideration.
CICS Configuration
The following example shows configuration for a single-session conversation. The
DFHPCT macro provides CICS with an application program name to retrieve the
program from a library and a transaction code to cause attachment of the program. The
transaction code is the LU 6.2 TPNAME:
lu62 DFHPCT TYPE=ENTRY,
PROGRAM=lu62prog,
TRANSID=tran
The CICS terminal control table defines the logical units to VTAM:
DFHTCT TYPE=INITIAL,
ACCMETH=VTAM,
APPLID=cics
:
DFHTCT TYPE=SYSTEM,
ACCMETH=VTAM,
MODNAME=cicslu62,
FEATURE=SINGLE,
SYSIDNT=tndm,
RUSIZE=1024,
Note. The SNAX/CDF APPLs used by SNAX/APC sessions must be configured with
CHARACTERSET ASCII. LU 6.2 protocols require the use of bit-oriented data for FM headers,
logical record lengths, and GDS variables. If these messages are translated into EBCDIC
(using the EBCDIC option), they will produce incorrect results.