CORBA 2.6.1 Programmer's Guide for C++

NSDOM_LOG_WARNING(pv_err_num, pp_text) ;
NSDOM_LOG_WARNING_ENV(pv_err_num, pp_text, pp_env) ;
In the above macros, exc refers to a CORBA exception, and env refers to CORBA environment.
Component Names
Each NonStop CORBA component should be assigned a unique component name so NonStop CORBA can identify the process that is logging
the error message. Component names are assigned once for each process, which must be done before an error message can be logged. If you
do not set the component name, the error logging facility assigns the default value
Application as the component name.
NonStop CORBA provides the following macro to perform component ID initialization:
NSDOM_LOG_SET_COMPONENT_NAME (ComponentName);
When using this macro, you supply your own ComponentName. The default name is Application. The predefined names listed below are used by
the NonStop CORBA components:
AdminServer
BSD
CommServer
EnvironServer
LSD
ILSD
InterfaceRepository
EventService
NameService
ConfigManagement
OTS
JTS
Message Logging Methods
Several NSDOM_Error_Log methods support setting component names and the logging of error messages. The following methods offer support
for logging Critical, Error, Warning, and Informational messages, as well as setting the component name and the log filename:
NSDOM_Error_Log::get_default().log_critical(__FILE__, __LINE__, \
pv_err_num, pp_text);
NSDOM_Error_Log::get_default().log_critical(__FILE__, __LINE__, \
pv_err_num, pp_text, pp_exc);
NSDOM_Error_Log::get_default().log_error(__FILE__, __LINE__, \
pv_err_num, pp_text);
NSDOM_Error_Log::get_default().log_error(__FILE__, __LINE__, \
pv_err_num, pp_text, pp_exc);
NSDOM_Error_Log::get_default().log_info(__FILE__, __LINE__, \
pv_err_num, pp_text);
NSDOM_Error_Log::get_default().log_info(__FILE__, __LINE__, \
pv_err_num, pp_text, pp_exc);
NSDOM_Error_Log::get_default().set_component_name(pp_comp_name);
NSDOM_Error_Log::get_default().set_log_file_name(pp_log_file_name);
NSDOM_Error_Log::get_default().log_warning(__FILE__, __LINE__, \
pv_err_num, pp_text);
NSDOM_Error_Log::get_default().log_warning(__FILE__, __LINE__, \
pv_err_num, pp_text, pp_exc);
Calling these methods causes the error logging facility to do the following:
Get the date, time, process name, process ID, and thread ID using system calls.
Get the exception information from the environment variable. The LOG_xxx_ENV macros extract the CORBA::Exception from the
environment variable and pass that to the methods as the exception parameter.
Compose a message using both user-supplied information and information gathered from the system.
Send an EMS message or record a message in the log file.
Error Numbers
Error numbers identify a problem that might occur in the NonStop CORBA environment. While NonStop CORBA reserves the error numbers
ranging from 0 through 6999, you can add user-defined error numbers in the numbers ranging from 7001 through 7100.
See the EMS Manual for details about error numbers.
Each error number is associated with the following information:
A symbolic name