fileset-ftp in 5.7 diff than 5.4.1

Just wanting to pick some brains on best practice in regards to using (or not using) fileset-ftp.

We recently went through an upgrade and though everything appeared to test out.   Apparently files were not ran completely through the process on the receiving app.

The original interface was designed to use fileset-ftp, ftp’s to the mainframe using ASCII.  

We found that if the outbound directory is not provided, the ftp errors.

Also found that the mainframe did not like the “.” as a directory, but we could use ~

The other thing appears that the endline characters may be getting changed (or not changed when they were previously).  I haven’t been able to get a clear answer as to what the line termination should be or what it is after transport as I do not have access to get the file and it is moved immediately.

In any case, still working through this, but wanted to get a take on best practices.   I am not fond of the use of ASCII as it leave some of the manipulation of data in the hands of something outside my control.

Since going to the mainframe, I would need to run the data throgh the hcitpstblconvert to convert the ascii data to EBCDIIC.  Not a problem and can then use “IMAGE”  

How are others handling… the 3rd option is to use a tcl proc to do the ftp, but I tend to hope that the tools in Cloverelaf will provide the funcitionality needed.

Ryan