CORBA 2.3.3 Programmer's Guide for C++

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●
A short description of the error●
A list of actions that you can perform to resolve the problem●