Description:
How to enable RV C client trace.

You could  trace various internal events by setting _RV_TRACING_MODULES to a list of modules and optional filters. The output file can be specified by setting _RV_TRACING_FILE.

Modules currently supported are:

DQ (no filter),
ADV (optional filter on advisory Subject)
RECV (optional filter on the send subject of messages).
CM
FT
EVENT


Specifying no filter is the same as specifying '>' but will be less intrusive because no matching is performed. Modules should be specified in a comma separated list, e.g.:

_RV_TRACING_MODULES=DQ
_RV_TRACING_MODULES=DQ,ADV

Note that most environments will require the list to be enclosed in double quotes to prevent their interpretation during the setting process. To provide more than one filter pattern just repeat the module.

 _RV_TRACING_MODULES=RECV=foo,RECV=bar

This will trace the arrival of messages on both 'foo' and 'bar'.

 
Examples:

1). On UNIX, a combination of module tracing can be done as the following.

export _RV_TRACING_MODULES="ADV=_RV.>,ADV=_HAWK.>,RECV,TIBRV,EVENTS,MSG"
export _RV_TRACING_FILE=”./RV_Hawk.trace.out”

Note that wildcards are accepted.

2). On Windows, the trace should be set in the following manner.

set "_RV_TRACING_MODULES= DQ,ADV=_RV.>,ADV=_RVCM.>,ADV=_RVCMQ.>,ADV=_RVFT.>RECV=_INBOX.>,RECV=<subject names that the DQ uses>"
set "_RV_TRACING_FILE=C:\trace1"


3). In TRA the trace should be set in the following manner.

tibco.env._RV_TRACING_MODULES=DQ,ADV=_RV.>,ADV=_RVCM.>,ADV=_RVCMQ.>,ADV=_RVFT.>RECV=_INBOX.>,RECV=<subject names that the DQ uses>
tibco.env._RV_TRACING_FILE=C:/tibco/<SOME_PATH>/cmqtrace.txt

All tracing will go to file cmptrace.txt

How to enable RV C client trace.