z/OS Communications Server: SNA Programming
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Categorization of data

z/OS Communications Server: SNA Programming
SC27-3674-00

The data available through the performance monitor interface is organized into major categories and subcategories as shown in Table 1. Typically, collection requests are made at the major category level, with the option of specifying multiple subcategories. Collect Performance Data CNM RUs can also combine major category requests, with some restrictions. Stop All Performance Data Collection CNM RU allows the monitor to stop all collections with one request. For virtual route data requests, specification of the resources to be controlled, or target resource set, is specified as follows:
  • A single VR (all Transmission Priorities included)
  • All virtual routes to a destination subarea
  • All routes.
For RTP connection data requests, the target resource set consists of all RTPs between the host VTAM® and a given CP in the network.
Table 1. Data categorization for performance monitor interface
Subcategory code Description
VTAM global data
Environment data Data related to this VTAM's characteristics
Installation-wide data Data related to installation-wide exits
Storage data Data related to this VTAM's usage of storage
Session data Data related to sessions and resource definitions
APPN directory services data Data related to directory services search requests
APPN topology data Data related to APPN topology and route calculations
CSM data Data related to the use of CSM storage and CSM buffer pools
Virtual route data
Basic route data Data related to individual virtual routes
RTP connection data
Basic RTP connection data Data related to individual RTP connections
Application data
Application data Data related to applications recovering from node failures, doing an MNPS planned takeover, or enabled for persistence in a sysplex that supports multinode persistent sessions
MNPS coupling facility structure data
MNPS coupling facility structure data Data related to the multinode persistent sessions coupling facility structure

To minimize the overhead incurred in data gathering, monitors should limit their collections to only those subcategories of interest and stop collections once they are no longer desired. However, data can only be retrieved while a collection is in progress.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014