That script is SO badly written that your errors could be comming from anywhere. Here's the output from the perl compiler on the command line (after I removed all the "==>" stuff): 
perl -c test.pl
Useless use of push with no values at test.pl line 224.
Unquoted string "aa" may clash with future reserved word at test.pl li
+ne 289.
Unquoted string "details" may clash with future reserved word at test.
+pl line 48
9.
Unquoted string "deny" may clash with future reserved word at test.pl 
+line 599.
Unquoted string "approve" may clash with future reserved word at test.
+pl line 64
8.
Unquoted string "aa" may clash with future reserved word at test.pl li
+ne 674.
Unquoted string "aa" may clash with future reserved word at test.pl li
+ne 770.
Unquoted string "adelete" may clash with future reserved word at test.
+pl line 10
11.
Unquoted string "adelete" may clash with future reserved word at test.
+pl line 10
56.
Unquoted string "aa" may clash with future reserved word at test.pl li
+ne 1250.
Unquoted string "fname" may clash with future reserved word at test.pl
+ line 1351
.
Unquoted string "lname" may clash with future reserved word at test.pl
+ line 1360
.
Unquoted string "aa" may clash with future reserved word at test.pl li
+ne 1599.
Unquoted string "aa" may clash with future reserved word at test.pl li
+ne 1630.
Name "main::bodyspec" used only once: possible typo at test.pl line 14
+72.
Name "main::month" used only once: possible typo at test.pl line 182.
Name "main::date2" used only once: possible typo at test.pl line 181.
test.pl syntax OK

[download]
I would suggest looking for something better (what the h*ll is this thing supposed to do anyway?)

Joost.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: CGI: Premature end of script headers by Joost
in thread CGI: Premature end of script headers by davidlt77

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.