Costas Anastassiades wrote:

> ...We're attempting an FTP transfer from a file with a record length of 56

> (i.e. REC= -56,,F,ASCII)  to a file with a record length of 100 (i.e.REC=
> -100,,F,ASCII).
> This is the FTP syntax we're using :
> GET <sourcefile> <targetfile> ;REC=-100,,F,ASCII

> The BUILD options work fine and targetfile *is* created with 100 byte
> records. BUT, the first record of the target file now contains the first
> record of the source file *plus* 44 bytes of the second record of the
> sourcefile and so on....
>
> In other words, it's seems to be ignoring the sources End-Of-Record
> markers, or it's not padding the remainder of the target record with
> spaces.
> ...

Costas,

I have not seen the new version and my FTP is limited, but could it be
something like a change in defaults:

eg. ASCII vs. BINARY - a Binary transfer might ignore file parms

or
 STRUCT - does it now support other file types (our version only supports
"file" - whatever that means - maybe they've added another type like "stream"
and defaulted to that).

I hope this helps,
Mike Patterson