continuous tracing

Document ID : KB000088749
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:

When is continuous tracing needed:

If traces of a situation, where the problem only occurs in a long time interval, are needed for further investigation.

For example: The issue occurs continuesly but in a long term interval, in order to find the root cause of the problem we need traces.
 
In these cases we reccomend using the "continuous tracing" (or in german rollierender Trace)
 
A "continues trace" is an automation that continuously starts and stops the writing of tracefiles, which means you will have a larger amount of tracefiles
but smaller in size.

A "continues trace" consists of  2 objects : a scriptobject 'SCRI.UC4_TRACE_SERVER' and a VARA-Object 'VARA.UC4_TRACE'

Resolution:

In these cases we reccomend using the "continuous tracing" (or in german rollierender Trace)
 
A "continues trace" is an automation that continuously starts and stops the writing of tracefiles, which means you will have a larger amount of tracefiles
but smaller in size.

 
A "continues trace" consists of  2 objects : a scriptobject 'SCRI.UC4_TRACE_SERVER' and a VARA-Object 'VARA.UC4_TRACE'
 
The scriptobject will periodically (:SET &NumberOfMinutes# = 10 in object SCRI.UC4_TRACE_SERVER) switch on a and off the needed traces.  
This will force the server to create new tracefile every for example "10 minutes".

 
Set the traceflags as needed for example :SET &MyTraceFlags# =  "2400000000000000" is a "TCPIP trace  2" and a "Database trace 4"

.png

The script will stay in status 'generating' until ended!

To stop the tracing simply edit the value from YES ton NO in the vara-object VARA.UC4_TRACE_SERVER
!NOTE only stop the tracing this way because if you stop manualy the tracing will still be active!!

 
File Attachments:
000008444.zip