Thank you for the response. I haven't tried this yet but I will shortley. The problem I'm having is first I have to search and grep for each rmtdb.lrl file because each server is different. This is what I'm working with for that purpose.

### Collect and parse rmt(*)db.lrl files.
my @dirs=qw(/bb/bin/jwarfel);
find(\&parse, @dirs);
   sub parse {
      if (/^rmt[1-9]|[1-9][1-9]|db.lrl$/) {
         copy("$_" , "$_.tmp");
         system "cat $_.tmp | cut -d ' ' -f1 > $_.tmp1";
         open $_, "< $_.tmp1";
         @$_ = <$_>; 
         close $_;
         unlink "$_.tmp", "$_.tmp1";
         foreach (@$_) {s/$_/\L$_/gi;}
         $rmtdb="$_";
         push(@rmtdbs , $rmtdb);
      }
   }

[download]

In reply to Re^2: Sting matching by jwesley
in thread String matching by jwesley

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.