6. DATA SOURCES › 6.3 Correlating Data Sources › 6.3.1 Correlating Data Sources to Reports
6.3.1 Correlating Data Sources to Reports
Each CA MICS Network Analyzer Option report, in tabular or
exception form, is built using data from a unique input data
source. The product does not attempt to mix data from more
than one source in any report.
Figures 6-1 and 6-2, Data Sources and Corresponding SNA
Network Reports, show which data sources are necessary for
which reports.
+----------------------------+--------+---------+-----------+
| Data Source/ | Record | Tabular | Exception |
| Record Description | Type | Report | Report |
+----------------------------+--------+---------+-----------+
|NPM: | | | |
| | | | |
| NPM Network Interval | SMF 28 | SNT208 |12001-12005|
| | +---------+-----------+
| | | SNT209 |12061-12062|
| | | SNT215 | |
| | | SNT216 | |
| | +---------+-----------+
| | | SNT401 |12121-12124|
| +--------+---------+-----------+
| NPM Network Monitor Event | SMF 28 | |12181-12209|
| +--------+---------+-----------+
| NPM Session Data | | SNT101 |12661-12663|
| | SMF 28 +---------+-----------+
| | | SNT103 |12780-12782|
| | +---------+-----------+
| | | SNT201 | |
| | +---------+-----------+
| | | SNT203 | |
| | +---------+-----------+
| | | SNT403 | |
+----------------------------+--------+---------+-----------+
| NetView Hardware Monitor | SMF 37 | SNT601 |12541-12542|
| or CA NetMaster NEWS | +---------+-----------+
| | | SNT602 | 12601 |
+----------------------------+--------+---------+-----------+
+----------------------------+--------+---------+-----------+
| Data Source/ | Record | Tabular | Exception |
| Record Description | Type | Report | Report |
+----------------------------+--------+---------+-----------+
| NetView Session Monitor | SMF 39 | SNT105 | 12301 |
| or CA NetMaster NTS with | +---------+-----------+
| 3274/3174 RTM | | SNT111 | |
| | +---------+-----------+
| | | SNT112 | |
| | +---------+-----------+
| | | SNT113 | |
| | +---------+-----------+
| | | SNT114 | |
| | +---------+-----------+
| | | SNT115 |12801-12802|
+----------------------------+--------+---------+-----------+
| NetView Accounting | SMF 39 | SNT211 |12852-12859|
| & Availability data | +---------+-----------+
| or CA NetMaster NTS | | SNT212 | 12862 |
| accounting data | +---------+-----------+
| | | SNT213 | |
| | +---------+-----------+
| | | SNT214 | |
+----------------------------+--------+---------+-----------+
| CA NetSpy NCP Interface | SMF n | SNT208 |12001-12005|
| | +---------+-----------+
| | where | SNT209 |12061-12062|
| | n is | SNT215 | |
| | user- | SNT216 | |
| |defined +---------+-----------+
| | | SNT401 |12121-12124|
+----------------------------+--------+---------+-----------+
| CA NetSpy VTAM Interface | SMF A, | SNT121 | |
| | S, T, +---------+-----------+
| | and U | SNT122 | |
| | +---------+-----------+
| | | SNT221 | |
| | +---------+-----------+
| | | SNT222 | |
+----------------------------+--------+---------+-----------+
| CA NetSpy General Alerts | SMF X | |12181-12195|
+----------------------------+--------+---------+-----------+
Creating Performance Classes for Reporting
------------------------------------------
Control units (3274s and 3174s) with the Response Time
Monitor feature installed measure end-user response time for
terminal sessions. This unique feature also allows you to
specify response time objectives as the percentage of all
transactions being less than a predetermined value (in
seconds). For example, a data center determines that the
terminals attached to control unit XYZ would provide adequate
service if 90% of all transactions have end-user response
times within three seconds. These objectives are defined to
NetView Session Monitor or CA NetMaster NTS and to the
control unit. If, during a predefined interval (such as 30
minutes), that objective is not met, the control unit and
NetView or CA NetMaster record the objective as missed.
Response objectives relate to NetView performance classes and
CA NetMaster RTM classes, both of which are referred to here
as performance classes. A performance class constitutes any
grouping the data center chooses. For example, all users on
the same link may belong to a performance class; or, all TSO
users may belong to a performance class. With NetView, the
data center defines the performance class service objectives,
then maps the terminal sessions to the appropriate
performance classes using the NetView MAPSESS definition
statement. With CA NetMaster, the Session Class definition
provides a similar function to the NetView MAPSESS definition
statement.
The following reports are based on site-defined performance
class:
o Exception Report 12301, Response Objective Missed for
Performance Class
o Tabular Reports
SNT105, NLDM Service by Performance Class
SNT115, NLDM Service by Performance Class
o Sample Graphic - Application Response by Performance
Class
o MICF Inquiries
SNTCD1, SNTPD1 - NetView Daily Avg Responses by
PCLASS
SNTCD4, SNTPD4 - NetView Daily % Resp Within Obj by
PCLS
For more information on how to establish and control NetView
performance classes, see the descriptions of the PCLASS and
MAPSESS definition statements in the NetView documentation.
For similar information on CA NetMaster, see the descriptions
of RTM classes and Session classes in the CA NetMaster
documentation.
Copyright © 2014 CA.
All rights reserved.
|
|