OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-7
Configuration Information in the OSI Manager MIB
Using Common Names to Identify OSI Addresses
OSI/AS allows you to identify the four components of an OSI address locally by using a
single name. This name is called an application name in OSI/AS and a common name
in FTAM.
Why Common Names Are Recommended
You should use common names for several reasons:
•
Common names simplify addressing for your applications by allowing all
addressing to be specified in a single line, through a single name.
•
Using common names instead of OSI addresses makes your system more flexible. If
you configure FTAM processes with OSI addresses and subsequently have to change
the addresses, you must then rebuild all applications that use those OSI addresses. If
you use common names and subsequently change the OSI addresses, you need only
update the definitions of the common names within the MIB of the OSI manager
process. Since the common name remains the same, you need not rebuild your
applications.
•
Common names are more descriptive, and easier to understand and remember, than
OSI addresses.
•
Common names are required if you define all OSI/AS addressing attributes under
the APPL ENTRY object rather than in TSEL and NSAP ENTRY objects.