Guardian-Ascii files (EDIT files) on the HP-nonstop are have an internal format, so when the file is download from the HP-nonstop it is converted to ascii by the SFTP server on the HP-nonstop and sends it in ascii format to my pc.
Once the file has been transmitted to my PC, the File is closed. The EOF of the file is = to the number of characters in the file on my PC.
I have noticed that when the EOF of the file on the HP-nonstop is less than the number of characters it takes to store the file on my PC, WinSCP sets the EOF of the file on my PC to be equal to that on the HP-nonstop, thus truncating text files.
Is Winscp checking the EOF before it downloads a file and then only downloads for the EOF size or is WinSCP downloading the file and then setting the EOF to the EOF from the source file?
However the ascii on the NonStop (Guardian EDIT file) is not pure text and can contain compressed lines, so the file's EOF is less that if the file was converted to a NL separated file (UNIX like). We believe that the tools that work correctly, just read until EOF is posted. The SFTP server on the NonStop converts the edit file to a UNIX text file on the fly) Since nothing on a windows box can read the contents of an EDIT file, a transfer in binary mode is not an option.
Is there a configuration I am not setting correctly that could resolve this problem?