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

NSDOM_CFG_TRACE_FULL_BUFFERING none
If STDOUT is
configured, sets
full buffering
on (default is
full buffering)
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
application processes. See the 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.3
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