Using System Logging [ Getting System Information Programmer's Guide ] MPE/iX 5.0 Documentation
Getting System Information Programmer's Guide
Using System Logging
System logging records the use of certain resources by accounts, groups,
and users. Like the administrative functions discussed in Chapter 7,
system logging can be used for billing purposes or for obtaining an
overview of system use.
Unlike these functions, however, system logging describes system use by
creating a running log of events, correlated with the job or session that
caused each event. System logging is the only means of recording system
use on a job/session basis.
For this reason, the system log can also be used for high-level
debugging. For example, the system log file can show whether an
error arose from a hardware or a software fault, or let you track
what an application did up to the point where an error occurred.
Instruction-level debugging is performed using the MPE/iX debug function.
For information on how to use it, refer to the MPE/iX System Debug
Reference Manual (32650-90013).
The majority of logging events are optional; when the system is
configured, the system manager can select whether they are recorded or
not. In addition to the LOGGING ENABLED event, the following events are
always enabled when the system is started:
* Type 100, log failure record
* Type 101, system up record
* Type 111, I/O errors
* Type 150, diagnostic information
* Type 151, high-priority machine check record
* Type 152, low-priority machine check record
For more information on enabling logging events, refer to the System
Startup, Configuration, and Shutdown Reference Manual (32650-90042).
The events that the system manager chooses to monitor are recorded on log
records contained in a disk file. Each event is recorded in one logical
record.
MPE/iX 5.0 Documentation