OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-11
PTrace
PTrace
You use the SCF management interface to start and stop the tracing of OSI/MHS
subsystem processes. The trace information is gathered in trace files. You use the
PTrace program to select, format, and display the trace data.
The PTrace Reference Manual gives general information about PTrace. For PTrace
information specific to OSI/MHS, see the OSI/MHS SCF Reference Manual.
ViewPoint
ViewPoint allows you to monitor the status of a network from a single terminal.
ViewPoint displays screens of information from local and remote subsystems, and
screens that display events reported by local and remote subsystems. You can also
enter commands to control the systems and subsystems in the network, using SCF
and other utilities. For more information on ViewPoint, see the ViewPoint Manual.
OSI/MHS Security Interfaces
OSI/MHS includes password server programmatic interfaces for MTA bind and MS
bind authentication. These interfaces let you develop custom security services for your
OSI/MHS subsystem.
MTA Bind Password Server Interface
If you develop a password server using the MTA bind password server interface, the
MR process sends a request to your application when initiating or accepting an
association with another MTA.
•
When initiating an association (bind request), the MR process passes the name of
the local OSI/MHS subsystem and the remote MTA and requests a password to
use in the bind request. Your application is expected to provide a password.
•
When receiving an association request (bind indication), the MR process passes
the local and remote MTA names and the password received in the request. It
requests that your server validate the password.
•
When responding to an association request (bind response), the MR process
passes the local and remote MTA names and requests a password to use in the
bind response. Your application is expected to provide a password.
•
When receiving the response to an association request (bind confirmation), the MR
process passes the local and remote MTA names and the password received in
the response. It requests that your server validate the password.
Your server can also provide functions other than those specifically requested.
You specify the presence of an MTA bind password server as an attribute of the
SUBSYS object.