CORBA 2.3.3 Programmer's Guide for C++

To start an alternate collector for the NonStop CORBA Software Developer Kit (SDK) environment, you enter the
following commands at the TACL prompt:
> EMSACOLL /NAME $xxx, NOWAIT/ BLOCKING OFF
For more information about starting the EMS collector, see the EMS Manual.
Note
The variable $xxx is the process name for the collector that you set using MY_COLLECTOR in the
$NSD_ROOT/etc/env.sh file or in log_file in the default@ORB entity in the configuration database.
Viewing NonStop CORBA EMS Messages
To view the NonStop CORBA EMS messages, you must enter the following commands at the TACL prompt:
> ADD DEFINE =_EMS_TEMPLATES, FILE $SYSTEM.ZORBSDK.newnres
> EMSDIST TYPE PRINTING, COLLECTOR $xxx, TEXTOUT $TERM1
where $TERM1 identifies a terminal of your choice.
Note
The ZORBSDK subdirectory in the example above is the Guardian subvolume where the SDK environment is
installed. If you are using the run-time kit, you should use ZORBRTK instead. The variable $xxx is the process name
for the collector that you set using MY_COLLECTOR in the $NSD_ROOT/etc/env.sh file or in log_file in the
default@ORB entity in the configuration database.
Examining EMS Messages
An entry from the EMS log looks like:
10:56 19MAR02 015,05,304 GIOP Proxy demarshal 0 profiles. Severity: Error,
Component: Application, PName: \ODIN.$:5:304, PId: 219086853, TId: 1,
File: proxy.cpp, Line: 388