OK.

First, you seemed to have confused everyone in your original post. We can proceed now that we all have a bit more information. Second, you should check out the Site How To for formatting tips. Just put your code in <code>...</code> tags. Third, my awk is really rusty so let me know if I misread your code.

Your file is only 33M so perl should have no problem provided you have some semblance of memory available to you. So can we assume that you do not need to do any pre-cutting?

In awk the input file is automatically read, parsed and acted upon. In Perl you have to explicitly tell perl how you'd like your file served. So when you say:

cat /home/spjal/files/bprcf.parms  /home/spjal/files/temp | 
perl ' BEGIN { linectr=0 }
         { linectr++
[download]

we would say:

#!/usr/local/bin/perl -w;
use strict;

my $infile = "/path/to/infile";
my $outfile = "/path/to/outfile";
open(INFILE, "$infile") || die "Died openning $infile. $!\n";
open(OUTFILE, ">$outfile") || die "Died openning $outfile. $!\n";

my $linectr = 0;
my $fline;
my $lline;
while(<INFILE>) {
    chomp;    # Remove the newline.
[download]

The while magic will now pull in the file line by line. I hope I understand correctly that the first line contains the four parms. Then:

    if(++$linectr == 1) {
        my($scheck, $echeck, $fcheck, $lcheck) = split;    # Splits on
+ whitespace by default.
[download]

Since I don't know the data you're processing I can't second guess your logic, so I'll Perl-ize the next bit:

      if ( $fcheck == $scheck )
        { $fline=2 }
      else
        { $fline=(($fcheck - $scheck) + 3) }
      if ( $lcheck == $echeck )
        { $lline=999999999 }
      else
        { $lline=(($lcheck - $scheck) + 3) }
    }
  elsif ( $linectr == 2 )
    { print OUTFILE "$_\n";    # $_ holds the line.
    }
  elsif ( linectr <= lline && linectr >= fline )
    { print OUTFILE "$_\n";
    }
}
[download]

That's what I understand from your response. I've written this as a stand alone script that can be called from your shell script. You can also run it inline by changing the hash-bang line with | perl -e '.... Please feel free to post more information or questions.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.