Consider use strict; at the top of your code.

my $second_file, my $counter etc are also good ideas.

Try print $second_file just before the open statement. Does it actually contain a filename?

Appears you're opening this file for output only. That's going to clobber whatever you got in there, so the next couple of <FH_SECOND> will have nothing to read as the file is opened for writing only - those lines will actually generate warnings.

Is the file actually "writable"? (Though I'm quite sure that's not your intention). When you do fix your open statement, ensure that the file's permissions are appropriate.

In reply to Re: File Handling problem by charlesboyo
in thread File Handling problem by girish_01

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.