CORBA 2.3.7 Programmer's Guide for Java

/* Log message where severity = INFORMATIONAL */
log_info(java.lang.Class pp_src_class, int pv_src_line_num, int pv_err_num,
java.lang.String pp_text)
/* Set component ID */
set_component_name(java.lang.String pp_comp_name)
/* Set log file name */
set_log_file_name(java.lang.String pp_file_name)
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 method to perform component ID initialization:
set_component_name (ComponentName);
When using this method, 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 com.tandem.nsdom.Config.Config_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:
Config_Log.log_critical()
Config_Log.log_error()
Config_Log.log_warning()