CORBA 2.3.3 Programmer's Guide for C++ (NonStop CORBA 2.3.3+)

NSDOM_LOG_INFO_ENV(pv_err_num, pp_text, pp_env) ;
NSDOM_LOG_SET_COMPONENT_NAME(pp_comp_name) ;
#define NSDOM_LOG_SET_LOG_FILE(pp_log_file_name) ;
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);