Understanding how real-time data is collected
Real-time data collection allows you to monitor performance of your network and system resources in an effort to resolve potential problems before they affect the user.
The IBM OMEGAMON for Networks on z/OS monitoring agent is designed to collect z/OS® TCP/IP and VTAM® performance data. You must run the monitoring agent on each LPAR being monitored. The agent monitors all of the TCP/IP address spaces running on the LPAR.
The monitoring agent can be used to collect several types of performance data, enabling you to monitor TCP/IP and VTAM address spaces, TCP/IP applications and connections, Communication Storage Manager (CSM) buffer pools, Enterprise Extender connections, FTP sessions and transfers, High Performance Routing connections, interfaces, OSA adapters, TN3270 server sessions, VTAM applications and sessions, VTAM buffer pools, VTAM environment, and z/OS Encryption Readiness Technology. Performance data is collected using the z/OS Communications Server network management interface (NMI), by querying SNMP MIBs and using the VTAM Performance Monitor Interface. The IBM OMEGAMON for Networks on z/OS monitoring agent is designed with performance in mind, providing an efficient mechanism for collecting large amounts of network performance data.
The total storage associated with real-time data collection includes the storage used in the monitoring agent address space as well as the data spaces listed in Table 1.
| Dataspace name | Size | Description |
|---|---|---|
| KN3ACTCS | 928 MB | This data space is used to store data that has been collected using SNMP, Performance Monitor Interface data, data collected using the z/OS Communications Server network management interface (NMI), the z/OS Communication Server external I/O control (IOCTL) function data, and Take Action command data. The storage area is reused each time the monitoring agent performs a collection. The actual amount of storage used is determined by the number of resources being monitored. |
| N3TCPIP | 2 GB | This data space is used to store data collected using the z/OS Communications Server network management interface (NMI). A maximum of 225 MB is used for VTAM data. A maximum of 225 MB for each TCP/IP address space is used for TCP/IP data. The storage area is reused each time the monitoring agent performs a collection. The actual amount of storage used is determined by the number of resources that are being monitored. |
| N3FTP | 2 GB | This data space is used to store data collected for FTP sessions and transfers. A maximum of 256 MB is used for each TCP/IP address space. Over time, all 256 MB is used because each new row of data is added to the existing data. When all 256 MB has been used, the data space wraps and new data is written to the beginning of the storage area. |
| N3TN3270 | 2 GB | This data space is used to store data collected for TN3270 server sessions. A maximum of 256 MB is used for each TCP/IP address space. The actual amount of storage used is determined by the number of resources being monitored. One record for each active session and one record for each session that closed in the last 24 hours is stored in the data space. |
The data spaces are created when the monitoring agent initializes and are deleted when the monitoring agent is stopped. The sizes are not configurable. However, the amount of storage used is determined by the number of TCP/IP address spaces and the types of data you configure the monitoring agent to collect.