You can capture FTP logon failures by using the session log facility
within FTP itself. The activity, when used, is logged to a source member
in a source physical file. What I've done is to run a program after the
FTP session completes scanning the member for certain key words that
indicate that a failure has happened and then take action once the
has been found.
I probably have some sample code around here if you'd like it.
Rich Loeber - @richloeber
Kisco Information Systems
On 3/27/2012 8:01 PM, James LeLeux wrote:
Hello all, new to the group, wandered over from the MAPICS board.
We are running V5R1 and have a CLP to capture login errors for SOX
purposes, but discovered we weren't capturing FTP login failures.
We tried various methods and could not get a bad FTP login to register an
error in the log.
Anyone have some suggestion on how to do this?
What triggered this was some stray routine appears to be disabling our FTP
profile and if we can log the time, that might help us trace the culprit.
Of course, once we saw FTP wasn't logged, we figured we needed to add it
our SOX data (because we don't have enough!).
This is only an internal account, the box is not exposed to the internet.
FYI - here's our syntax:
DSPLOG PERIOD((*AVAIL &CHRDTE) (*AVAIL &CHRDTE)) +
OUTPUT(*PRINT) MSGID(CPF2234 CPF1393)
Thanks in advance for any insight!
BTW - no cracks about the V5R1, we just ordered a new box with V7R1 -
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