Donna suggested that I try removing the spaces, but to no avail.  Using the
following I get the same results.  BTW this problem is somewhat
inconsistent.  It didn't show up until I put in the last set of IF
statements.  Taking them out had no effect.   A few months ago I  had a
similar problem with a command file, but since the output was going to the
screen I took the cheap and sleazy way out and skipped over the 2 or 3 blank
lines. 



   67     !        echo!rec>>*IT2
   67.4   !          echo!rec>*REJECTF
   67.6   !          echo!rec>>*REJECTF
   68.4   !        echo!rec>*REJECTF
   68.6   !        echo!rec>>*REJECTF
   73     !      echo!rec>*IT2
   75     !      echo!rec>>*IT2

-----Original Message-----
From: Donna Garverick [mailto:[log in to unmask]]
Sent: Thursday, February 15, 2001 4:36 PM
To: [log in to unmask]
Subject: Re: ECHO Problem


"Black, Cory" wrote:

> The problem is that ECHO is writing 2 lines, the data followed by a
> blank line.  The relevant code follows.
>
>    67     !        echo !rec >> *IT2
>    67.4   !          echo !rec > *REJECTF
>    67.6   !          echo !rec >> *REJECTF
>    68.4   !        echo !rec > *REJECTF
>    68.6   !        echo !rec >> *REJECTF
>    73     !      echo !rec > *IT2
>    75     !      echo !rec >> *IT2

i think i know the problem :-)

being the tidy folks that we are, we like to see spaces around our
operators.
*but* when using echo *everything* is echo'd.  so that pretty space after
'!rec'
is also getting echo's to the fixed length files.  i strongly suspect '!rec'
is
already a full 79 bytes long and <oops> there's an extra character!  what to
do
with it??  put it on a new record.  try removing the extra space and see if
that
doesn't help :-)         - d 'already bitten by this'

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

"Unix _is_ user friendly.
It's just very selective about who its friends are.
And sometimes even best friends have fights."

>>>MY opinions, not Longs Drug Stores'<<<