|
Loyd, You wrote: ******************************************************************* from: "Goodbar, Loyd (ETS - Water Valley)" <LGoodbar@xxxxxxxxxxxxxx> subject: RE: FTP server side logging? Hi Rob, I'm already looking at the FTP exit points, V5R2. The information center shows 3 exit points for FTP: client request validation, server request validation, and server logon. None of these shows me the command issued by the client. >From my XP box: ftp> put me.savf loyd/me What I see in the FTP server request validation exit point (VLRQ0100 format): Application ID: 1 (ftp server) Operation ID: 7 (receive file from client) Operation information: /QSYS.LIB/LOYD.LIB/ME.FILE (requested target path) Nowhere do I see "put me.savf loyd/me" I want to see/log the actual put command (or any other command) the client issues. I would write this information to a log file on the iSeries. Thanks, Loyd ************************************************************************ Loyd, Have you written a logging routine into your invocation of FTP? How this is done depends on if, when you say "server", your talking about a PC or the AS/400. Its pretty easy on the iSeries. I do it by using REXX to call the FTP commands in a separate file and log the output to another file. I can then examine the log file with REXX and look for certain FTP codes or character strings and make my REXX program do operations accordingly. In addition, the log file can be a permanent or temporary log depending on your needs. The same sort of thing could be done on a PC or whatever platform invokes the FTP as long as there is a native language for you to create utilities (scripts, execs, whatever you call them). If this is the kind of thing your talking about and you need to know more, let me know. Take care, Dave Odom Arizona
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.