OSI/MHS Management Programming Manual

Password Server Interfaces
OSI/MHS Management Programming Manual—424824-001
7-45
MPS Error and Informational Messages
The algorithm used by the MPS to search the Authorization information is described in
the header file for the authorization module. (See MPS Source and Configuration Files
on page 7-65.)
Another factor that influences performance is the audit -trail option. It is most efficient
to disable that option during normal operations. If you suspect a problem or have some
other requirement for auditing, you can run an MPS in ISOLATE mode with the
auditing option on. For bind operations, no file I/O is required.
Note that the MS bind password server interface is a WAITED interface for the message
store. The MS process will not be able to service any request from any source if it is
awaiting the reply to a request from the MPS process.
The MPS configuration that provides optimal performance is one MPS process per MS
group.
MPS Error and Informational Messages
The next several pages describe the errors, warnings, and informational messages that
MPS processes print on the output file. The messages are listed in alphabetical order
with error messages first, informational messages second, and warning messages third.
Cause. This message reports a process or device-related I/O problem.
Effect. It is fatal and causes the MPS to ABEND.
Recovery. This message should never occur in normal operation. If you are using the
MPS unmodified (as delivered from Compaq), contact your Compaq representative with
information about your configuration and the circumstances of the error.
Cause. This message reports a process or device-related I/O problem.
Effect. It is fatal and causes the MPS to ABEND.
Recovery. This message should never occur in normal operation. Contact your
Compaq representative with information about your configuration and the circumstances
of the error.
Cause. This message refers to a problem using the TMF facilities.
Effect. Generally, the MPS will attempt to continue processing under these conditions,
but any requests from OSI/MHS will be rejected.
*** ERROR *** $RECEIVE not open
*** ERROR *** AWAITIOX received error <value> on $RECEIVE
*** ERROR *** BEGINTRANSACTION failed with error <value>