Real-time TCP/IP packet and data trace NMI (SYSTCPDA) |
Using this interface, applications can obtain
a copy of network packets (for example, packet trace records) or data
trace records that are buffered by the TCP⁄IP stack's
packet or data trace functions. The packet trace function, data trace
function, or both must be enabled with the VARY TCPIP,,PKTTRACE command
or VARY TCPIP,,DATTRACE command. See z/OS Communications Server: IP System Administrator's
Commands for more information about using the Vary command. |
Real-time TCP connection SMF NMI (SYSTCPCN) |
Using this interface, applications can be notified
when TCP connections are established or terminated in a near real-time
fashion. SYSTCPCN provides applications with a copy of records indicating
a TCP connection initiation or termination. These records are presented
in the same format as SMF type 119 TCP connection initiation and termination
records (for example, subtype 1 and 2 records). The interface can
also be used to provide records describing existing TCP connections.
This interface does not require TCP⁄IP SMF recording
to be active. |
Real-time TCP/IP OSAENTA trace NMI (SYSTCPOT) |
Using this interface, applications can obtain
copies of network packets and records that are buffered by the TCP/IP
OSAENTA trace functions. The OSAENTA Trace function must be enabled
using the VARY TCPIP,,OSAENTA command. See z/OS Communications Server: IP System Administrator's
Commands for more information about using the Vary
command. |
Real-time SMF NMI (SYSTCPSM) |
The records provided through the interface are
type 119 SMF records. The specific subtypes that are provided are: - FTP client transfer completion records (subtype 3)
- TCP/IP profile event record (subtype 4)
- TN3270E Telnet server session initiation and termination records
(subtypes 20 and 21)
- TSO Telnet client connection initiation and termination records (subtypes
22 and 23)
- DVIPA status change and DVIPA removed records (subtypes 32 and
33)
- DVIPA target added and removed records (subtypes 34 and 35)
- DVIPA target server started and ended records (subtypes 36 and
37)
- CSSMTP event records (subtypes 48 - 52)
- FTP server transfer completion records (subtype 70)
- FTP daemon configuration records (subtype 71)
- FTP server logon failure records (subtype 72)
- IKE tunnel and dynamic tunnel event records (subtypes 73 - 78)
- Manual tunnel activation and deactivation records (subtypes 79
and 80)
Except for the MVS™ SMF
header, these records are identical in format to SMF records created
by TCP⁄IP. Some fields in the MVS SMF
header are not set.
These records offer several key advantages
over SMF records: - They do not require that TCP⁄IP SMF record
capturing is activated.
- They are presented to the application in a buffered format (for
example, when several SMF records are created within a short time
interval, they are collected and passed to the application as a group
of records instead of individual records).
In addition to these records, more records are available
across this interface that are not currently available from TCP⁄IP SMF records
processing: - FTP server transfer initiation records (subtype 100)
- FTP client transfer initiation records (subtype 101)
- FTP client login failure records (subtype 102)
- FTP client session records (subtype 103)
- FTP server session records (subtype 104)
See Real-time SMF NMI: FTP SMF type 119 subtypes 100-104 record formats for the
structures and mappings of records 100 through 104.
|