CORBA 2.6 Programmer's Guide for Java

application processes. See the NonStop TS/MP System Management Manual for information on PATHCOM
commands.
To disable tracing, reverse the earlier modification, then restart the processes. You should disable tracing as soon as
your troubleshooting is completed because tracing can consume resources and produce considerable output.
Using the Console to set tracing is the easiest method, but this method offers limited choices for tracing and sets tracing
for NonStop CORBA subsystem processes, not application processes. See the NonStop CORBA 2.6 Administration
Guide for general information about using the Console. The tracing choices offered in the Console are:
None●
Basic●
Detailed●
Table 53 shows the available trace settings. The Basic and Detailed columns show the settings that are set by using
the Console. You can set any of the trace setting individually as described below.
If you want more specific control over the individual trace settings than is provided through the Console, you can set a
value in the configuration database by using the cfgmgt tool. The entity default@trace contains names and
values for the various trace settings. If the value is TRUE, tracing is enabled for NonStop CORBA components affected
by the trace flag setting. (The Naming Service uses the setting for trace in the entity
NS@name_service_settings.)
You can also modify the $NSD_ROOT/bin/nsdstart script. This script contains NonStop CORBA subsystem
trace-flag settings that have been commented out. Like the Console, the nsdstart script sets tracing only for
NonStop CORBA subsystem processes, not application processes. To enable tracing for one or more of the subsystem
processes, you must uncomment the appropriate lines before running nsdstart.
An example of one of these lines is as follows:
[ set server env NSDOM_CFG_TRACE_ORB=TRUE
Removing the open bracket ([) uncomments the line.
When you enable tracing by using an export statement, you can set individual environment variables as shown by this
example:
export NSDOM_CFG_TRACE_PROXY=TRUE
Clearing the environment variable is done by using the unset statement. For example,
unset NSDOM_CFG_TRACE_PROXY
Caution: You need to be very careful to keep changes made with the Console and changes made to the
nsdstart script consistent with your intentions. If you have used the Console to change trace
settings, those changes will not be reflected in nsdstart.
Table 5.3. Tracing Options for NonStop CORBA subsystem
Services
Item
Basic Tracing sets these
environment variables
Detailed Tracing sets these environment
variables
Default log
Filename
BSD
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_SOCKEH
bsd.log