CORBA 2.6 Programmer's Guide for C++

tracing. In some cases, an operator must work with other operators on remote systems to discover configuration
mismatches.
For a more general understanding of NonStop CORBA component interactions, architecture, and message flows, see
Appendix A, Architectural Walkthrough.
Using the Error Logging Facility
Unexpected conditions detected by NonStop CORBA can be logged through the Event Management Service (EMS)
on NonStop systems. Looking at the log messages is one of the first things to do when troubleshooting a problem.
Often the source of a problem can be ascertained readily from information contained in the log.
Refer to the EMS Manual for background information and usage questions about EMS.
When logging is directed to EMS, the NonStop CORBA error logging facility operates in an OSS environment and
uses EMS to report log information. The NonStop CORBA error logging facility provides an API that you use to
write NonStop CORBA exceptions and error conditions to an EMS collector.
You can configure log messages to go to STDOUT, STDERR, a log file, or EMS. You can use the data recorded in the
log file to help you track and fix problems that occur during the execution of your NonStop CORBA applications.
The error logging facility shields you from the details of error logging. You need not be concerned with the error-log
file format or with creating, opening, and closing the error log.
Design of the Error Logging Facility
The error logging facility is implemented in the NSDOM_Error_Log object. This object provides several methods
for logging error conditions. When you call a method in NSDOM_Error_Log, the method creates the log message
and performs the appropriate operations to write the message to the configured destination.
The error logging facility composes a log message based on both data you supply and data that NSDOM_Error_Log
obtains during the call.
Note: The error log is also used internally by NonStop CORBA; messages written to the error log by your calls
will be interspersed with messages generated by NonStop CORBA.
Each time a log entry is generated, the error logging facility writes an error message to the configured destination.
You specify an alternate collector as described in Starting an Alternate NonStop CORBA Collector.
An EMS collector must be started before you can write to it. Refer to the EMS Manual for details about starting and
running the EMS collector.
Information in the Error Log
Table 5.1. Error Log Information
Field Description Field Name
Date and time the exception was logged No field name
Error number for this entry No field name
Text description of the exception No field name
Severity level of the exception Severity
Name of the component that logged the error Component
Name of the process that logged the error PName