If your log file are organized in that order, (I mean "WORKSTATION" and "exit code" come one by one and in a fixed order), then you can just use: 
#!/usr/bin/perl
use warnings;
use strict;

open my $fh, '<', 'log.txt' or die "cant open log.txt:$!";

my $workstations;
while (<$fh>) {
    next if /^\s*$/;
    if (/(WORKSTATION\d+)/) {
        $workstations = "$1(Line $.)";
    } elsif (/(User program exit code:\s*\d+)/) {
        print "$workstations $1(Line $.)\n";
    }
}

[download]

If "WORKSTATION.." is at the beginning of a line as it seems to be in your example, change the regex to ^(WORKSTATION\d+) which makes it better/faster to suit your problem. so does 'User program exit code:' line...

Regards

lihao(XC)

In reply to Re: Parsing a Log file by lihao
in thread Parsing a Log file by nashkab

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.