CORBA 2.3.3 Programmer's Guide for C++

Naming
Service
NSDOM_CFG_TRACE_ORB
NSDOM_CFG_TRACE_POA
NSDOM_CFG_TRACE_POA
NSDOM_CFG_TRACE_PROXY
NSDOM_CFG_TRACE_ORB
NSDOM_CFG_TRACE_GIOP_FW
NSDOM_CFG_TRACE_GFSEH
NSDOM_CFG_TRACE_GCFEH
ns.log
OTS
NSDOM_CFG_TRACE_ORB
NSDOM_CFG_TRACE_POA
NSDOM_CFG_TRACE_OTS
NSDOM_CFG_TRACE_POA
NSDOM_CFG_TRACE_PROXY
NSDOM_CFG_TRACE_ORB
NSDOM_CFG_TRACE_OTS
NSDOM_CFG_TRACE_GIOP_FW
NSDOM_CFG_TRACE_GFSEH
NSDOM_CFG_TRACE_GCFEH
ots.log
XID
Broker
NSDOM_CFG_TRACE_ORB
NSDOM_CFG_TRACE_POA
NSDOM_CFG_TRACE_OTS
NSDOM_CFG_TRACE_POA
NSDOM_CFG_TRACE_PROXY
NSDOM_CFG_TRACE_ORB
NSDOM_CFG_TRACE_OTS
NSDOM_CFG_TRACE_GIOP_FW
NSDOM_CFG_TRACE_GFSEH
NSDOM_CFG_TRACE_GCFEH
ots.log
Calling the Trace Facility
To generate a trace message, you call the predefined trace macro or the log_trace() or trace() method defined
in the NSDOM_Trace object. The call must be complete with the required parameter values. The trace facility then
creates a trace message and writes the message to an ASCII trace file.
The trace file information and other configuration data used by the trace facility must be specified in the NonStop
CORBA configuration before the call (see How to Enable Tracing).
Trace Macros
The macros shown below are provided to simplify the task of adding trace statements to your application code.
/* log trace message */
NSDOM_trace ( const char *pp_data,
short pp_data_len,
CORBA::Environment &pr_env );
/* printf style trace output */
NSDOM_tracef ( const char *pp_format, ...);
This macro opens the trace file and writes the trace message. If you use this macro, you do not need to make direct
calls to the NSDOM_Trace object.
Note
To specifically close the trace file, you must call NSDOM_Trace::close_trace_file(). If you do not call this
method, the trace facility closes the trace file when the current process exits.