There’s a few issues with the DS 1.2.0 Traces CSV format that make it incompatible with MS Excel (and, I suspect, other tools also):
1. Date format
Because all fields are 2 digits, Excel can’t tell which is the year (human readers may also get it wrong due to US/RoW confusion about mm/dd or dd/mm)
A 4-digit year needs to be used.
2. Time format
Excel doesn’t recognise this as a time, because of the colon between seconds & decimal seconds.
It needs to be a decimal point here.
3. Time width
The width of the decimal seconds varies between 1 & 3 digits - which breaks the tabulation, and makes the plain text file hard to read.; eg,
11/02/04,15:32:55:984 - 137;ADL;7;[L3] same PLMN 11/02/04,15:32:55:98 - 138;ADL;7;02 03 04 01 00 FF 11/02/04,15:32:56:0 - 001;ADL;7;[L3] plmn_change_timer_cb 11/02/04,15:32:56:0 - 002;L3RR;3;==>C RRC_TIM_PERIODIC_SI 11/02/04,15:32:56:15 - 003;L3RR;3;<==C PH_BCCH_REQ on 27 11/02/04,15:32:56:150 - 004;L3RR;3;C: S4 P0 N1 M10
This also means that the above problems can’t be worked around by importing as fixed-width fields.
The Trace strings themselves need to be “quoted” in some way - so that semicolons within the text are not takn as delimiters!
Or, again, the preceding fields need to be fixed width.