OSI/AS Configuration and Management Manual

Introduction
OSI/AS Configuration and Management Manual—424119-001
1-9
MIB
MIB
The MIB (Management Information Base) is a key-sequenced file that contains
management information for the subsystem. Two types of information are included in
this database: Local Management Information Base (LMIB) information and Local
Directory Information Base (LDIB) information.
The OSI manager process writes configuration information (LMIB) to the MIB as you
add and configure subsystem components. When you start the OSI manager process, it
reads the information contained in the MIB to retrieve the values of a previous
configuration.
The LDIB contains optional information on applications. When you register a local or a
remote application with the OSI manager, the OSI manager stores the following
information:
•
The name you wish to use locally to refer to the application. This name is optional.
•
The applications complete OSI address (in other words, the PSAP—the NSAP,
TSEL, SSEL, and PSEL together). This address uniquely identifies the application,
both within the OSI/AS subsystem and within the OSI environment.
When an application requests session, presentation, or ACSE connections, the OSI
manager uses the information in the MIB to select the processes that service the request,
and to specify configurations for the different layer services.
OSI/AS Services to User Applications
Your application programs are the users of the OSI/AS subsystem. User applications are
not part of the subsystem itself; they are location-independent with respect to other
subsystem components. That is, applications that use the services of a subsystem can run
in any processor within the same NonStop system, or within any NonStop system in an
Expand or a FOX network.
OSI/AS provides applications with direct access to ACSE services, Presentation Layer
services, and Session Layer services, as well as indirect access to Transport Layer and
Network Layer services. Application programs can directly request and receive the
services of the upper three layers through the APS (application, presentation, and
session) procedures. The requests from procedure calls are passed by the API
(application programmatic interface) to the various processes of an OSI/AS subsystem.
These calls thus provide application programmers with a procedural interface to the
subsystems services. For a description of this interface, see the OSI/AS Programming
Manual.
This subsection contains the following topics:
•
Access to ACSE, Presentation Layer, and Session Layer on this page
•
Transport Layer Access on this page
•
Network Layer Access on page 1-10
•
Selecting Processes on page 1-10