CORBA 2.6 Programmer's Guide for Java

NSDOM_CFG_TRACE_OTS none
NSOTS or
application
transaction
activity
NSDOM_CFG_TRACE_PROXY
NSDOM_CFG_TRACE_PROXY_DETAIL
orb_proxy
ORB proxy
processing:
method dispatches
and results of
method
invocations. If
detail, the
GIOP messages
NSDOM_CFG_TRACE_THREADS threads
NonStop CORBA
thread framework
NSDOM_CFG_TRACE_TIMER event_time
NonStop CORBA
timer objects
NSDOM_CFG_TRACE_DETAIL none
Sets verbose
tracing
NSDOM_CFG_TRACE_FULL_BUFFERING none
If STDOUT is
configured, sets
full buffering on
(default is full
buffering)
NSDOM_CFG_TRACE_PI
NSDOM_CFG_TRACE_PI_DETAIL
pi
Traces basic
Portable
Interceptor
activity. If
detail, add
data
representation
during portable
interceptor
processing
ssl
NonStop CORBA
SSLIOP activity
How to Enable and Disable Tracing
You can enable tracing by using one of the following techniques:
Use the NonStop Distributed Component Console. The Console updates the configuration database. The Console
can only change trace settings for NonStop CORBA subsystem processes, not user application processes.
Use the cfgmgt tool to modify the configuration database directly.
Modify the $NSD_ROOT/bin/nsdstart script.
Set the environment variables before starting the processes by using an export statement.
Tracing starts at process initialization, so you need to start or restart the process you want to trace after you have
enabled tracing. You can use the Console to start and stop NonStop CORBA subsystem processes, or you can use
Guardian or PATHCOM commands. The Console manages NonStop CORBA subsystem processes, but not user