Connection monitoring mapping statement

Telnet collects monitoring data for any client connection that is mapped to a MONITORGROUP Object. The collected data can be retrieved several ways:

• Display the data for a single connection using the D TCPIP,tnproc,TELNET,CONN,CONN=connid command.
• A network management agent can request the data from the Telnet SNMP subagent, after the subagent is started by specifying the TNSACONFIG statement. TCPIPJOBNAME must be specified for the subagent to connect with the agent. For information about the TNSACONFIG statement and the parameters needed to start the subagent, see z/OS Communications Server: IP Configuration Reference. For details about configuring the SNMP agent, see Simple Network Management Protocol.
• The Network Management Interface (NMI) Application Programming Interface (API), EZBNMIFR, can be used instead of SNMP to retrieve the data. In this case, the TNSACONFIG statement is not needed. For details about configuring EZBNMIFR and the parameters needed to issue the call, see z/OS Communications Server: IP Programmer's Guide and Reference.
• The Telnet SMF119 session termination record contains two optional sections that can be used to retrieve life-of-session performance data. Life-of-session data is a subset of life-of-connection data. Sliding-window data is not available because data is reported only at the end of the session and not at periodic intervals. One optional section contains response time statistics (excluding sliding-window) and a second optional section contains response time counts by time bucket. For details on the Telnet server SNA session termination record, see z/OS Communications Server: IP Programmer's Guide and Reference.

The MONITORGROUP Object statement in BEGINVTAM is used to set the criteria for monitoring. Options allow the inclusion or exclusion of averages, counts by time bucket, and whether or not the IP network should be included in measurements. When a MONITORGROUP is mapped to Client Identifiers with the MONITORMAP mapping statement, the requested data will be collected for those connections.

Up to 255 MonitorGroups can be active at one time for all ports per Telnet instance. When 255 MonitorGroups are active, no additional groups can be created until some groups are no longer in use by Telnet. A MonitorGroup is considered no longer in use when the group is not defined in a current profile and no connections are using the non-current profile where the MonitorGroup was defined. After being notified that no entries are available, it is up to the operator to manage the removal of some entries by ending connections to free a profile. The operator does not get a notification when an entry becomes available.

Each MonitorGroup entry in the table is assigned an index number. The index number coincides with one of the 255 slots available in the MonitorGroup table. Each Telnet connection entry saves the index number of the MonitorGroup mapped to the connection. When the management application queries a connection for data, it can also query the MonitorGroup table to get the group name and configuration values based on the index found in the connection entry. With the data from the connection and the MonitorGroup criteria from the MonitorGroup table, a management application can generate several summary reports. If a management application is not being used to collect the connection monitoring data, the D TCPIP,tnproc,TELNET,CONN,CONN=connid command can be used to view all the collected data and MonitorGroup information for a single connection.