The following should be reasonably efficient. It does keep files open, one per unique DESCR element. Depending on how many DESCR elements you have in your real data, you may need to rethink this, possibly with a least-recently-used scheme.

use warnings;
use strict;

my %fh_of; # Hash of filehandles

foreach my $file (<R*-*.txt>) {
    open INPUT, "<$file" or die "Couldn't open $file: $!";
    while (<INPUT>) {
        my $fh;
        if (/^DESCRP\s+(.+?)$/) {
            my $des = $1;
            unless (exists $fh_of{$des}) {
                 open $fh_of{$des}, ">>$des.txt"
                    or die "Couldn't open $des.txt: $!";
            }
            $fh = $fh_of{$des};
            $file =~ /^(R.+?)-/; # Glob guarantees match
            print $fh "$1$des\n";
            next;
        }
        print $fh $_ if $fh;
    }
    close INPUT;
}
close $_ for (values %fh_of);

[download]

With the input files as you've given them, I get the expected output. All errors are fatal; you might want to handle them more gracefully depending on your application. If an input file does not start with a DESCRP line, $fh will not be defined, so I just throw away records until I see a DESCRP line. Again, you may want to handle this differently.

In reply to Re: Reorganizing file contents by rjt
in thread Reorganizing file contents by tomdbs98

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.