I usually process similar files line by line, keeping the status (project, job) in a variable that survives the loop. It is not clear from your description whether a job can have more than one type and file, so I assumed it can't.
#!/usr/bin/perl
use warnings;
use strict;
sub output {
my ($id, @jobs) = @_;
print join("\t", $id, @{$_}{qw(JOBID TYPE FILE)}), "\n" for @jobs;
}
my @jobs;
my $id;
while (<>) {
my ($tag, $value) = m{<(.*)>(.*)</\1>} or next;
if ('PROJECT_ID' eq $tag) {
output($id, @jobs);
$id = $value;
@jobs = ();
} else {
$tag =~ s/[0-9]+$//;
$#jobs++ if 'JOBID' eq $tag;
$jobs[-1]{$tag} = $value;
}
}
output($id, @jobs); # Don't forget to output the last job.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.