We have a legacy system that uses Perl for the glue. The system generates .bat files in a CGI environment and then uses the SYSCALL of Perl to execute the.bat files and pipe them into a .txt file that can be reviewed in the CGI environment to watch them run and ensure successful execution.

The system has relied on the following code running on Windows Server 2000 for years -->

$hldcmd = "$pathcc" . "\\" . "$hldbat" . " \> " . "$pathcc" . "\\" . +"$txtname" . ".txt"; open(SYSCALL, "$hldcmd |");

We are moving to Windows Server 2003 Release 2 SP 2 and the system calls do not work. Is this a known issue? If so are there work arounds. Please note I have no controll over the environment.

Thanks Tim

In reply to Perl SYSCALL by tim.mcintosh

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.