Quantcast
Viewing all articles
Browse latest Browse all 3189

(DP) Support Tip: setting CRS debugs via omnisv

in some instances it is necessary to capture CRS and/or MMD debugs.

one of the simplest ways to get the CRS and MMD threads is to run omnisv in debugs mode

ex:

omnisv -start -debug 0-200 dbg.txt

this will write debugs including CRS/MMD to the default location which is to the Omniback/tmp location

you can use all of the debug varaibles here as well

change location

omnisv -start -debug 0-200 C:\temp\dbg.txt

circular

omnisv -start -–debug 1-200,C:30000  CircularDBG.txt  

 

The complete debugging command is as follows :


-debug 1-99[,C:n][,T:s][,U] XYZ [host]

where:

1-99 is the debug range. Specify the range 1-99 unless instructed otherwise. Specify optional parameters as a part of the range parameter, separated by commas:

C:n limits the size of debug files to n kilobytes. The minimum value is 4 (4 kB) and the default value is 1024 (1 MB).

T:s is the timestamp resolution, where the default value is 1, 1000 means the resolution is one millisecond and 0 means timestamps are turned off.

On some platforms (for example, on Novell NetWare), millisecond resolution is not available.

U is the Unicode flag. If it is specified, the debug files on Windows are written in the Unicode format.

XYZ is the debug postfix, for example DBG_01.txt.

host is a list of clients where debugging is turned on.

 


Viewing all articles
Browse latest Browse all 3189

Trending Articles