OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-11
How Configured Information Is Used in Making
FTAM Associations
Configuration of Remote Responders
If your applications use remote common names, you must also configure these common
names and their corresponding OSI addresses in the OSI manager MIB. For remote
addresses, you need to configure only the common name and the OSI address
components; no servers or profiles are required. However, if desired, you can also
configure remote Layer 5, Layer 4, and/or Layer 3 profiles, describing the connection
characteristics imposed by the remote entity. These profiles will then take precedence
over the local profiles. For details, see the OSI/AS Configuration and Management
Manual.
How Configured Information Is Used in Making FTAM Associations
Once the subsystems are configured, the APLMGR and OSI manager processes retrieve
configured information from their respective MIBs whenever this information is needed
for making an association. The following subsections describe how this information is
used. Step by step, they explain what occurs when a Tandem initiator services an
application’s request for an FTAM association, and when a Tandem responder services a
request from a remote FTAM responder.
To understand the step-by-step descriptions, you need to know the following terms:
•
Subdevice: A subdevice allows communication between a process at a particular
OSI layer, such as an FTAM initiator or responder, and the local Tandem OSI server
process (TAPS, TSP, or NSP) that provides the services of the next lower layer. Each
subdevice handles one association or (at layers below ACSE) one connection.
•
Register request: A register request is a request, made by the FTAM or OSI/AS
API on behalf of an application, to establish an association or connection or (at the
OSI/AS level or below) to wait for an incoming association or connection. Servicing
an FTAM register request includes selecting an available initiator process.
•
Attach: A request to wait for an incoming association or connection is called an
attach.