OSI/MHS Management Programming Manual

Password Server Interfaces
OSI/MHS Management Programming Manual—424824-001
7-24
MPS Concepts and Components
The audit-trail file can be a disk file, a terminal, or a spooler location. If it is a disk file,
it is an Enscribe entry-sequenced file with a record size of 250 bytes.
When auditing is enabled, the audit-trail file is created and shared by all active MPS
processes that support the same master user (except that if the audit-trail file is a spooler
location, each MPS process opens a separate spooler location). You can disable auditing
for a single process or for all processes that use the audit-trail file; each affected process
closes the file as it becomes aware of the configuration change.
You can also disable logging of specific types of information. For instance, you can
disable logging of Bind requests or specify that passwords be omitted from all records
written to the audit-trail file.
Each record created in the audit-trail file contains the information shown in Table 7-9
:
Note. An MPS audit-trail file is unrelated to a TMF audit-trail.
Table 7-9. Contents of Audit Trail File
Field Description
timestamp A character string containing the local system time when the MPS
process responded to the request in the form “HH:MM:SS
DDMMMYY”. This field has a fixed length of 16 characters.
ApplName A character string containing the SCF APPL name of the APPL
involved. This field has a fixed length of 16 characters (blank padded)
requestType A character string containing the type of request made of the server:
•
Bind
•
Register-MS
•
ADD
•
ALTER
•
DELETE
This field has a fixed length of 11 characters (blank padded).
result A character string containing the result of the request: either
“accepted” or “rejected”. This field has a fixed length of 8 characters.
MPSprocessName A character string containing the process name of the MPS process.
The format of the name is: “\node.$proc”. This field is a fixed length
of 15 characters (blank padded).