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 TimIn reply to Perl SYSCALL by tim.mcintosh
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |