It's not a direct answer to your question but since script1.pl and script2.pl are obviously perl scripts (and I assume you can edit them), I would 'wrap' their code in a module and start like 
# untestest
# ...
use lib1 qw(sub_for_perl1);
use lib2 qw(sub_for_perl2);

#...
sub_for_perl1($file_in, $file_out);
if ( -e $file_out) {
    sub_for_perl2($file_out, $final_out);
}

[download]
or similar. So you can benefit from a better error handling etc. (It could be possible your result file isn't there because script1.pl fails already.)
I use this approach often since I try to avoid calling scripts from other scripts, if possible.

k

In reply to Re: Synchronizing Multiple System Processes by klekker
in thread Synchronizing Multiple System Processes by neversaint

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.