To Tom - It appears that the FTP server has already done some work with the incoming request - it has resolved names into full IFS paths - if the item doesn't exist, that value in the operation-specific operation just has to be blank.

There is apparently nothing that gives you the actual server subcommand that was sent in - which WOULD have what you want.

Do you get the operation identifier? The remote IP address?

So it seems all you can log is an attempt to do something, but with a non-existent file, for example.

I have a crazy thought - maybe you can use the QIBM_QTMF_SVR_LOGON exit point to start a comm trace between the IP address and your server, you'd process it only if you get a failed request. The actual incoming packets would be included in the output of the trace.

I don't know if there is an issue with pairing up logon and request - I suspect they are in the same process, so it'd be safe to assume all fits together. Maybe each time you get a logon, start the trace. Each time there is a request, end it, process it, and start another one, until the session ends - OOPS - seems you don't get an indication of when the client asks to QUIT!

Of course, you can always put in a requirement to include the actual FTP subcommand in the operation-specific operation!


On 10/20/2012 5:16 AM, Jack Kingsley wrote:
So is all your logging that your getting then just host generated commands
that you get(puts, gets).

On Fri, Oct 19, 2012 at 5:58 PM, Tom Hightower <tomh@xxxxxxxxxxx> wrote:

I've got an FTP exit program in place to control logins, and to record the
various commands processed by the FTP server on the iSeries:

Exit point: QIBM_QTMF_SERVER_REQ Format: VLRQ0100
Program: #FTPLOGON4

The program logs "gets" gets (among commands). Well, mostly. it records
SUCCESSFUL gets. If a PC user (for example) issues a get on a non-existent
file, nothing is recorded. All of the successful gets are recorded just

Is there something in the program I should look at to enable logging of the
unsuccessful commands?


This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page