OSI/FTAM Configuration and Management Manual

Introduction to Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
1-8
OSI/AS, OSI/TS, and TLAM, PAM, X25AM, or
TCP/IP
OSI/AS, OSI/TS, and TLAM, PAM, X25AM, or TCP/IP
Part of the overall Tandem FTAM architecture are the services provided by
OSI/Application Services (OSI/AS), OSI/Transport Services (OSI/TS), and one of the
following data communications subsystems: the Tandem LAN Access Method (TLAM)
for D-series systems or, for G-series systems, the Port Access Method (PAM); the X.25
Access Method (X25AM); or Tandem NonStop TCP/IP. To communicate with remote
computer systems across an OSI network, you must configure these subsystems to
operate with Tandem FTAM. Figure 1-3
on page 1-9 shows the major components of
these subsystems.
The OSI/AS subsystem consists of Tandem application, presentation, and session
service provider (TAPS) processes; the OSI/TS subsystem consists of transport service
provider (TSP) processes; and the TLAM, PAM, X25AM, and TCP/IP subsystems each
consist of network service provider (NSP) processes. All these subsystems are managed
by the OSI manager process, which has a management information base (MIB) separate
from that of the APLMGR process.
When you are configuring these subsystems, you must register each TAPS, TSP, and
NSP process to be used in support of FTAM with the OSI manager process. You can
have more than one instance of each of these processes running in an OSI/AS
subsystem, as well as multiple OSI manager processes managing separate subsystems.
For more information on these entities, see the OSI/AS Configuration and Management
Manual.
The OSI manager MIB contains a local directory information base (LDIB) that stores
the common names and corresponding addresses for all OSI processes. In addition to the
address information for the TAPS, TSP, and NSP processes, you must add either the
common name or the address associated with each Tandem initiator or responder
process to the OSI manager MIB. Section 3, Planning, Installing, and Configuring
Tandem FTAM, provides details on how to add this important naming and addressing
information.