Skip Mode Enhancement for the FlexNet RL Parser

Previously, when the FlexNet RL Parser encountered corrupted data, it would fail and halt the parsing process. To address this issue, the latest release introduces a new server property called skipmode , that enables the parser to continue processing the RL file uninterrupted, even when corrupted data is encountered. Unlike the initial implementation, which terminated upon error, this enhancement allows the parser to skip over corrupted lines, log the errors, and proceed with parsing. This not only ensures a smoother parsing experience but also improves transparency and error tracking.

Configuring skipmode in the RL Parser Configuration File

When skipmode is set to false in the configuration file, the parser behaves as it did previously. If an error is encountered, the parser halts at the corrupted line and does not proceed further, and the error is recorded in the log file with a message stating failed to parse input line number xxx.

When skipmode is set to true in the configuration file, the parser continues processing the RL file even when it encounters corrupted lines. Each error is logged with detailed information, including the error type and timestamp. For example: Failed to parse input line number 675 "time:"2025-03-18T17:05:16+05:30. Corrupted data is logged into JSON files. The number of JSON files generated corresponds to the number of sections in the RL file. Each section has its own log file. When a section ends, its log is archived with a timestamp, and a new JSON file is created for the next section. This process continues until the RL file is fully parsed.

For more information on the FlexNet RL Parser, see the FlexNet RL Parser User Guide.