If I was doing this, I'd write a state machine to help me parse the file. I'd use regexen to match the relevant lines and extract information out of them. Based on the limited info you provided, I'd use states like "StartAction", "StartSubtask", "SubtaskOptions", "Job", "EndSubtask", "EndAction", etc.

Unless you set out to create a parseable grammar, you might run into problems but since you have control over the grammar as well as the parser you should be able to fiddle with things and make them work.

-sauoq
"My two cents aren't worth a dime.";

In reply to Re: Multiline log parsing by sauoq
in thread Multiline log parsing by Jenda

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.