This step is necessary if the UTM application was running with more than one process during recording, a scenario that generally applies in the case of UTM applications running at medium or high load.
In this step, the binary BTRACE files of all UTM processes are sorted and entered in a common BTRACE file on the basis of their timestamps. This process step must always run on the same platform as step 1 (UPIC Capture).
On Unix, Linux and Windows systems, you must use the UTM utility program kdcsort to perform this step, see below.
This step results in a sorted binary BTRACE file that contains all the trace entries in the correct temporal sequence.
You can use the provided BTRACE example procedure for sorting.
Utility program kdcsort
The utility program kdcsort reads the trace entries from multiple BTRACE files and writes the trace records in the correct temporal sequence to an output file. It is started as follows:
On Unix and Linux systems, from the shell with
utmpath/ex/kdcsort btrace_out btrace-1 btrace-2 ... btrace-n
On Windows systems, from a command prompt window with
utmpath\ex\kdcsort btrace_out btrace-1 btrace-2 ... btrace-n
Meaning of the parameters
btrace_out Name of the output file to which the sorted trace records are to be written.
btrace-1 btrace-2 ... btrace-n
Names of the recorded BTRACE files. At least two files must be specified.
The file names must be specified separated by spaces.
The output file from kdcsort can then either be prepared as a common list for all UTM work processes using the UTM utility program kdcbtrc or be further processed using the program UpicAnalyzer.