Unknown SYST 'AIX'

Question

We are getting the following two warnings from FTPFileFactory:

WARN: Unknown SYST 'AIX' - defaulting to Unix parsing
WARN: Could not detect format. Using default UNIX

I noted this post had a similar issue:

http://www.enterprisedt.com/forums/viewtopic.php?t=3188

The response suggests creating a "custom listing parser". This leads to my first two questions:
1) Would this "custom parser" subclass your FTPFileParser?
2) Is there any documentation to help with doing that? The Javadoc for that class is sparse.

Let me now take a different approach. Based on the coding I see in FTPFileFactory, it looks like only "WINDOWS", "UNIX" and "VMS" are currently understood as O/S name responses to SYST.

However, "AIX" is a flavor of unix. And it seems that defaulting to UNIX parsing worked just fine. One of our vendors changed their servers to AIX six weeks ago. These WARNs are now logging hundreds per day, but things are processing fine. So clearly the existing UnixFileParser() can cope with an AIX flavor of dir listings.

http://en.wikipedia.org/wiki/IBM_AIX

This leads to my next (and most important) question:

3) Would you consider updating your FTPFileFactory to accept "UNIX" -or- "AIX" as a SYST response and then use the UnixFileParser for both?

Thanks.

Answer 1

Yes, we'll change the parser to accept AIX or UNIX for the Unix format.

Answer 2

We've now changed the code - next release will have this fix.

Answer 3

Thanks! You ROCK! :D

Answer 4

Do you have any projected date for your next release (of edtFTPj/PRO)?

Answer 5

It's planned to be in early March. Email us if you want a prerelease to try out.

Answer 6

Awesome, that info helps, thank you!

I may have a similar issue to this related to a z/OS SFTP server. We've gotten them to stop sending EBCDIC, but there still seem to be issues with unicode chrs and dir listing parsing. I'm still running down those details and will start a separate thread for that when I have enough info. Any pointers to relevant threads or docs would be appreciated.

Answer 7

You can set the encoding for both the data channel and the control channel.