Exchange/SNA Manual

Configuring SNAX/XF for Exchange/SNA
Installation and Configuration
6–2 104700 Tandem Computers Incorporated
Configuring SNAX/XF
for Exchange/SNA
This subsection outlines the system generation definition requirements and SCF
commands required to use a SNAX/XF data communications line with
Exchange/SNA.
Note If you are using SNAX/CDF rather than SNAX/XF, do not follow the instructions in this section. Instead
refer to the subsection “Configuring SNAX/CDF for Exchange/SNA,” later in this section.
Defining SNAX/XF Data
Communications Lines
.To use Exchange/SNA, you must define a SNAX/XF communications line and, if one
has not been previously defined, a SNAX/XF service manager process. Only one
SNAX/XF service manager process is allowed on a Tandem system. Therefore, if one
has already been defined on the system, you do not need to define another one.
For information on how to define a SNAX/XF data communications line, see the
System Generation Manual, Volume 2, the section “SNAX Access Methods.”
Exchange/SNA has few requirements for the entries in the system generation
configuration file (the input to the SYSGEN program). Those requirements are
described below.
Configuration Modifiers
The modifiers given below apply only to the line-handler process. Only those
modifiers for which Exchange/SNA requires a specific value are described.
SECONDARY
defines the SNAX/XF line as an SDLC secondary station. This value is required
for Exchange/SNA.
ASCII (or omit TRANSLATE)
specifies that SNAX/XF is not to translate the data sent or received over the line.
This value can be overridden by individual LUs if necessary. You should never
specify TRANSLATE ON, since Exchange/SNA sends and expects to receive data
in EBCDIC code. (The ASCII and TRANSLATE OFF parameters are equivalent.)
In addition, note that the values you specify for MAXPUS and MAXLUS must match
their equivalent parameters in the ACF/VTAM SYSGEN specification. Each
Exchange/SNA subsystem requires one PU and from two to six LUs.