... XML::Smart ...

I wouldn't :) 

use XML::LibXML 1.70; ## for load_html/load_xml/location
my $qstat = 'qstat.xml';
my $dom = XML::LibXML->new(qw/ recover 2 /)->load_xml( location => $qs
+tat );
for my $job ( $dom->findnodes( q{   /job_info/queue_info/Queue-List   
+ } ) ){
    print $job->nodePath, "\n";
    for my $slot ( $job->findnodes( q{   ./job_list/slots    } ) ){
        print $slot->nodePath, "\n";
        print $slot, "\n";
        print $slot->textContent, "\n";
    }
}
__END__
/job_info/queue_info/Queue-List
/job_info/queue_info/Queue-List/job_list/slots
<slots>1</slots>
1

[download]

Re: parsing xml, xpather.pl/htmltreexpather.pl

Also , if you're going to post xml, make sure its well-formed first

In reply to Re: Parsing XML output from `qstat` by Anonymous Monk
in thread Parsing XML output from `qstat` by Macslayer

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.