MVSFORUMS.com

[devpal]

Hi,

Currently, I am trying to FTP a sequential file from mainframe to Unix. the file length is 228 bytes. The last few fields are fillers for some records, and there is no data in these records for the fields even before the fillers.

There are invalid values in these fields.. Some junk characters.. When I FTP the file, the users who receive the file say that they are not getting a Fixed byte format file. The records are of different lengths.

Can the presence of invalid data in some of the fields, cause the record length truncation? Or, is there something to do with the parameters that we are passing in mainframe?

Currently , we are using the ASCII format, but, we even tried with BINARY.

In the case of ASCII, when we get the FTP file back from UNIX, we could see extra lines in the file with invalid values after record that has invalid values.

In the case of Binary, when we get the FTP file back from UNIX, we cannot see any records. All the records have some junk again..


Please could you help me with this problem.


Thanks,
Devpal.

[superk]

I would start by making sure that you are not truncating trailing blanks. You can specify the option TRAILINGBLANKS TRUE in your FTP.DATA dataset, or, by using the command LOCSITE TRAILINGBLANKS.

Beyond that, I would take a hex dump of the ASCII file from the Unix machine and verify the actual data contents and validate that the records are fixed in length at 228 bytes.

[warp5]

Did you have PTF's recently installed in your system? There is a TCPIP FTP Ptf that is in error and can cause a problem like this. Try using a SENDSITE before the PUT and if that solves the problem, maybe you need PTF UK01739 (or is that the APAR number ?)