You are not checking the return cordes on any of your IO operations. I find it hard to belive that you are "at a loss" before doing even one round of debugging. any robust Perl code should ALWAYS check the return codes.
It should look like:
mkdir "c:/configs/".$RackID or die "mkdir failed: $!";
open ERROR,">c:configs/$RackID/AP Compare results.txt" or die "open fa
+iled: $!";
...
pedantics would check returns on the print and the close, but I'd bet dollars to donuts that your problem is in the mkdir or the open. My first guess would be that the program lack permission to write into the configs directory.
-pete
"Worry is like a rocking chair. It gives you something to do, but it doesn't get you anywhere."
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.