I’m not familiar with Fileset/FTP in Cloverleaf, but many FTP programs have trouble with some quirks in how the AS400 handles FTP.
For a database file, you would need to request the file as LIBRARY/FILE.MEMBER, which means that, for example, the file BADPLPP in library BSYDTAA would be specified as BSYDTAA/BADPLPP.BADPLPP. Most database files have one member, usually named the same as the base file name. However, they can have multiple members, and since the member name follows the period, it looks to some OS’s and FTP programs as if it’s an extension. If Cloverleaf is looking for a particular set of allowed extensions, that could really throw it.
This only applies to the database files. Other files in the IFS follow much more normal naming conventions.
There is alternate naming convention for database files, which can be selected with the NAMEFMT 1 command (from the client, usually given as QUOTE SITE NAMEFMT 1). Under this naming convention, database files are all in the /QSYS.LIB directory, all the library names end in .LIB, all the FILE names end in .FILE, and all the member names end in .MBR. So the same file example would be /QSYS.LIB/BSYDTAA.LIB/BADPLPP.FILE/BADPLPP.MBR.
In either case, the member is really the thing treated like a file, and the file is treated as a directory. The only difference between the two naming formats is, well, the naming format.
All of which is to say, if the Cloverleaf FileSetFTP doesn’t support this, you may be able to give it a few more options to make it do what you want.
One convenience tip: If the first thing you do is to CD to a certain directory expressed in the alternate naming convention, the AS400 FTP server will switch to that convention for you rather than requiring you to give the NAMEFMT 1 command. This gets around those FTP clients which make it hard to supply customized commands to an FTP server.
Of course, then there’s the special case of AS400 SAVE files….
