W3C Input Format Parameters
The W3C input format supports the following parameters:
| iCodepage | ||
| Values: | codepage ID (number) | |
| Default: | 0 | |
| Description: | Codepage of the log file. | |
| Details: | 0 is the system codepage, -1 is UNICODE. | |
| Example: | -iCodepage:1245 | |
| dtLines | ||
| Values: | number of lines (number) | |
| Default: | 10 | |
| Description: | Number of lines examined to determine field types at run time. | |
| Details: | This parameter specifies the number of initial log lines
that the W3C input format examines to determine the data type of the input record fields. If the value is zero, all fields will be assumed to be of the STRING data type. For more information on how field data types are determined, see W3C Input Format Fields. |
|
| Example: | -dtLines:50 | |
| dQuotes | ||
| Values: | ON | OFF | |
| Default: | OFF | |
| Description: | Specifies that string values in the log are double-quoted. | |
| Details: | Some W3C log files enclose string values within double-quote characters ("). | |
| Example: | -dQuotes:ON | |
| separator | ||
| Values: | a single character | space | tab | auto | |
| Default: | auto | |
| Description: | Separator character between fields. | |
| Details: | Different W3C log files can use different separator characters
between the fields; for example, Exchange Tracking log files use tab characters, while
Personal Firewall log files use space characters. The "auto" value instructs the W3C input format to detect automatically the separator character used in the input log(s). |
|
| Example: | -separator:tab | |