CGI error debugging can get really whacky. I feel your pain.
I would try breaking that one long print statement into several smaller print statements.
Maybe then you can get a more meaningful error.

You are using the standard syntax when you might want to try the object-oriented syntax,
Try ...
my $cgi = new CGI;

print $cgi->header(),
      $cgi->start_html('Test the boundaries of Relaxation'),
      $cgi->p('Hello Weekend'),
      $cgi->end_html;

[download]
Also, are you sure you want your shebang line(#!) to be:
#!/user/bin/perl -wT
and not
#!/usr/bin/perl - wT

I hope this helps.
Get Strong Together!!

BTW - does anybody know why a shebang of:
#!/user/local/bin/perl
works on my machine?
I have no /user directory, so I would expect an error, but I got none. Is something going on under the hood?

In reply to Re: Premature Error using CGI.pm by aardvark
in thread Premature Error using CGI.pm by ZydecoSue

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.