Is that the code you're actually running? I'm thinking your FIND constant is actually defined as 'MC9' so when you execute the following line, you just print the input_record_separator (which you earlier defined as FIND) once for each line your script reads in.

print IO::File->input_record_separator while $fh->getline;

[download]

I'm not familiar with IO::File but that's my best guess as to what you're seeing.

Something like this should work for your purposes:

use strict;
use warnings;

my $filename = 'search.txt';
my $find = 'MC9';

open(FILE, '<', $filename) or die "Cannot open file: $!";

while (my $line = <FILE>) {
    print $line if $line =~ /$find/;
}

close(FILE);

[download]

In reply to Re: reading and working with grow.out files by Riales
in thread reading and working with grow.out files by rmgzsm9

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.