EZA1479I

File transfer might be incomplete -  Last record received
without EOL  sequence
Explanation
 The user requested a file from the server.  The
FTP client was receiving the  file while ENCODING was set to MBCS.
 The server sent the file without  appending <CRLF>, the FTP
end of line (EOL) sequence, to the last record. The  FTP client configured
MBREQUIRELASTEOL TRUE,  so the client considers this to  be an error.
The file transfer might not be complete.

System action
 The FTP client sends an ABOR command to the server.
 The FTP client  continues.

Operator response
 No action needed.

System programmer response
 If the sender of the file was not
a z/OS® CS FTP server, consult
the vendor of  that product for more information.   If the vendor
indicates that the last  record does not include an EOL marker, use
the LOCSIte subcommand with  the NOMBREQUIRELASTEOL
parameter set to change the MBREQUIRELASTEOL setting, then get the
file again. If the problem continues, contact the vendor. 
 If
the sender of the file was a z/OS CS
FTP server, the transfer is  incomplete.  z/OS FTP appends an EOL marker to the final
file record of  multibyte files unless you have overridden the sender's
EOL marker using the  server's MBSENDEOL configuration option.  Use
the stat subcommand to query the  server's MBSENDEOL
setting.   If  MBSENDEOL is not CRLF,  use the site 
subcommand with the MBSENDEOL=CRLF parameter set to change the server's
MBSENDEOL  setting, then get the file again. If  MBSENDEOL is CRLF,
save the output from the stat subcommand and the LOCSTat subcommand,
and contact the IBM® support
 center.  
 See the information about the MBREQUIRELASTEOL and MBSENDEOL configuration options in z/OS Communications Server: IP Configuration
Reference. See the information about using the stat, site, LOCSTat, or LOCSIte subcommands
in z/OS Communications Server: IP User's Guide and
Commands.
 For z/OS FTP
products, see  the information about  support
for MBCS languages in z/OS Communications Server: IP User's Guide and
Commands for information about configuring z/OS FTP for multibyte transfers.
For other FTP implementations, consult your vendor for more information.

User response
 Inspect the file to determine if the transfer
was complete. If the transfer is not complete, contact the  system
programmer.

Problem determination
 Not applicable.

Source
 z/OS Communications
Server TCP/IP: FTP

Module
 Not applicable.

Routing code
 Not applicable.

Descriptor code
 Not applicable.

Example
  EZA1460I Command:        
locsite mbrequirelasteol 
EZA1460I Command:                                                            
get /tmp/test8.txt 'user1.test8.txt' 
EZA1701I >>> PORT 9,42,105,36,4,42                                              
200 Port request OK.                                                            
EZA1701I >>> RETR /tmp/trash/test8.txt                                          
125 Sending data set /tmp/trash/test8.txt                                       
EZA1490I Error writing to data set                                              
EZA1479I File transfer might be incomplete - Last record received without EOL sequence                                                                         
>>>ABOR                                                                         
426 Connection closed; transfer aborted.                                        
226 Abort successful.                                                           
EZA2108I Confidence=Low for GET of USER1.TEST8.TXT                        
EZA1460I Command: 