We're running CFT 2.6.2 on AIX and Windows 2003.  Most files transfer fine, but we're having issues doing a transfer of a particular file from Unix to Windows.  The file contains multiple record types and each record type has its own record length with the largest record length at 2146 chars wide. When we try to do the transfer as ascii it writes a 0 byte file on the Windows side and we get this error on the Unix side:

[Internal]
Local Diagnostic Code: 108
Description: File read error
[Complementary]
SFM_GET : other error (see extended fields)                                                                                                                    
[Protocol]
00000034

We get this error on the Windows side:

[Internal]
Remote Diagnostic Code: 600
Description: File input/output error
[Complementary]

[Protocol]
ABO 213

If we specify binary the file transfers, but the file format gets changed and the file is unusable.

The Sender CFT will default to value of 512 when no Record Length is provided with variable length files in UNIX, The Record Length parameter is used to allocate memory for when CFT reads the record into memory to send to the partner. The error that is issued here (return code 108) indicates that the memory segment allocated is to small for the record read.

The solution on the sender side is to add a flrecl number greater than the largest record length. As an example use 5000 in the flrecl.. When using implicit send/receive templates please remove the Implicit flag until tested.