If you can afford to slurp the file into memory/into a scalar, split is very handy. Just one additional statement as corrective measure does not hurt clarity. 
$_ = q{stuff before
myrecordsep
field1=item1
field2=item2
...
myrecordsep
field1=item9
field2=item10
...
};

@chunks = split /myrecordsep\n/;
# /(?=myrecordsep\n)/   in case you want to keep the sep in the chunk
Dump @chunks;
shift @chunks; # discard the first if not needed

__END__

$VAR1 = 'stuff before
';
$VAR2 = 'field1=item1
field2=item2
...
';
$VAR3 = 'field1=item9
field2=item10
...';

[download]
(update: lookahead)
Wiki | CPAN Testers wiki

In reply to Re: Change the behavior of Perl's IRS by daxim
in thread Change the behavior of Perl's IRS by LighthouseJ

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.