I tried this: 
use Proc::Queue size=>2, qw(run_back);
Proc::Queue::trace(1);

my @ARGV = ("file1.fasta","file2.fasta");

for ( @ARGV  )
{  run_back
   {
      eval{  run_code($_) };
      print STDERR $0."[$$]: $@\n" if $@;
   }

}
1 while wait != -1;

run_code {
  my $file = shift;
  #do the rest
}

[download]
It gives this: 
Proc::Queue::run_back(CODE(0x824a9d0)) called at mycode_itr.pl line 37
Proc::Queue::fork called at mycode_itr.pl line 37
Proc::Queue::run_back(CODE(0x824a9d0)) called at mycode_itr.pl line 37
Proc::Queue::fork called at mycode_itr.pl line 37
Proc::Queue::wait called at mycode_itr.pl line 38

[download]
Is it correct or is it an error message? If correct, what does it mean? However, now it does show 2 instances under "top".
Regards,
Edward

In reply to Re^4: How to Run Script for Multiple Files in Parallel? by monkfan
in thread How to Run Script for Multiple Files in Parallel? by monkfan

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.