You can trap the following:
You can set up event detectors to trigger alerts and actions on receipt of events.
To trap FTP failures, use an FTPFAIL monitor. To trap other EDS events, use a CUSTOM monitor.
The EDS events that are issued when an FTP, Telnet, or connection event takes place are listed in this table.
Event |
Event Name |
Object |
Resource |
Reference |
Message ID |
Client/ Server |
---|---|---|---|---|---|---|
FTP Retrieve |
$IP.FTPLOG.RETR |
Remote IP address |
Data set name |
FTP server name |
IPFM2103 |
S |
FTP Store |
$IP.FTPLOG.STOR |
Remote IP address |
Data set name |
FTP server name |
IPFM2103 |
S |
FTP Store Unique |
$IP.FTPLOG.STOU |
Remote IP address |
Data set name |
FTP server name |
IPFM2103 |
S |
FTP Append |
$IP.FTPLOG.APPE |
Remote IP address |
Data set name |
FTP server name |
IPFM2103 |
S |
FTP Logon Failed |
$IP.FTPLOG.LOGONF |
Remote IP address |
|
FTP server name |
IPFM2102 |
S |
FTP Delete |
$IP.FTPLOG.DELETE |
Remote IP address |
Data set name |
FTP server name |
IPFM2104 |
S |
FTP Rename |
$IP.FTPLOG.RENAME |
Remote IP address |
|
FTP server name |
IPFM2105 |
S |
FTP Retrieve Failure |
$IP.FTPFAIL.RETR |
Remote IP address |
Data set name |
FTP server name |
IPFM2113 |
S |
FTP Store Failure |
$IP.FTPFAIL.STOR |
Remote IP address |
Data set name |
FTP server name |
IPFM2113 |
S |
FTP Store Failure Unique |
$IP.FTPFAIL.STOU |
Remote IP address |
Data set name |
FTP server name |
IPFM2113 |
S |
FTP Append Failure |
$IP.FTPFAIL.APPE |
Remote IP address |
Data set name |
FTP server name |
IPFM2113 |
S |
FTP Delete Failure |
$IP.FTPFAIL.DELETE |
Remote IP address |
Data set name |
FTP server name |
IPFM2114 |
S |
FTP Rename Failure |
$IP.FTPFAIL.RENAME |
Remote IP address |
Old data set name, new data set name |
FTP server name |
IPFM2115 |
S |
Telnet connection started |
$IP.TNLOG.START |
Remote IP address |
Telnet LU name |
Application name |
IPCM2002 |
S |
Telnet connection started |
$IP.TNLOG.START |
Remote IP address |
Telnet client job name |
Telnet client node name |
IPCM2013 |
C |
Telnet connection stopped |
$IP.TNLOG.STOP |
Remote IP address |
Telnet LU name |
Application name |
IPCM2003 |
S |
Telnet connection stopped |
$IP.TNLOG.STOP |
Remote IP address |
Telnet job name |
Telnet client node name |
IPCM2014 |
S |
Connection started |
$IP.CONNECT.START |
Remote IP address |
Client job name |
Client job name |
IPCM2311 |
- |
Connection stopped |
$IP.CONNECT.STOP |
Remote IP address |
Client job name |
Client job name |
IPCM2312 |
- |
CA TCPaccess CS for z/OS message received |
$IP.AXSLOG. |
Severity code |
CA TCPaccess CS for z/OS SSID |
CA TCPaccess CS for z/OS message number |
CA TCPaccess CS for z/OS message number |
|
For more information about the format of FTP records and how SMF exits are invoked, see IBM’s Communications Server IP Configuration Guide.
For more information about FTP reply codes, see RFC 959, File Transfer Protocol .
Copyright © 2012 CA. All rights reserved. |
|