The List Objects (QUSLOBJ) API is easy to use and is your best choice for a beginning point.

You would create a user space, call QUSLOBJ to build a list od objects in the user space, and then loop through the space to retrieve basic information about each object that you listed. (User Space APIs)

You would have a display file with a subfile. Each object that you retrieved information about from the space would be written to your subfile. You would enter options in your subfile to choose which objects to send to the FTP server.

When you call QUSLOBJ, you pass in a library and object name parameter. You can request objects with a specific name or a generic* name or a special value such as *ALL to list all objects in the library. You also pass in an object type, which would probably be *FILE since this is for FTP.

The User Space APIs take a little practice, but you can ask questions to help with those.

As long as you are working with /QSYS.LIB file system objects, the QUSLOBJ API is the one you want first.

However, if you are thinking of listing streamfiles in a /root directory or other directory, then QUSLOBJ won’t help you at all. For that, you’ll need to work in some very different ways.

Tom

Some APIs return the information to a user space, which does get more involved — but again, once you’ve blazed a trail, it’s much easier from that point.

You could use the API’s to write your own WRKOBJ type program & display file, but the API’s can be quite difficult and time consuming to get working correctly. If you just need something quickly, you’re better off using the PDM method. If you need something permanent that will be used by other people, then it’s probably worth writing your own tool for this.

You could also use DSPOBJD to an output file instead of the API’s, this would probably be quicker to get working and you could always replace it with the API’s at a later date.

Regards,

Martin.