Previous Topic: 3.3.3.3 Cluster Population Summary ReportNext Topic: 3.3.3.5 Sparse Cluster Population Report


3.3.3.4 Data Value Exception Detail Report


This is a simple listing of any observation that contains one
or more outlying data values.

The application will determine the key sequence structure of
the input file, modify the key structure to remove date and
time key values except for the End Timestamp, and present the
listing using the modified key sequence. You can optionally
exclude the CA MICS account codes from the reports by
specifying a value of "NO" to the REPORT USING ACCOUNT FIELDS
option on the Clustering Execution Options screen. This
report can be used to verify that the outliers are truly
exceptional, and not merely unusual workloads.

Note that each outlying clustering data value is flagged with
an "*".  This allows you to identify outliers in the data and
understand which elements(s) contained abnormal data
values.

A sample Data Value Exception Detail report is shown below in
Figure 3-36.

Data Clustering Analysis Data Value Exception Detail For: Monday, June 23, yyyy Listing of Observations With Outlier Values System Job Job Job TCB CPU Identifier DIVISION DEPARTMENT RESERVED Group Identification End Time Stamp Time DASD EXCPS ------------------------------------------------------------------------------------------------------------ XAL1 BNK 01622 ******** 7 FCSBK150 07NOVyy:10:08:53.48 0:01:49.84* 65,053* DEV 01056 ******** 7 LTSIPCSX 14NOVyy:17:54:24.33 0:40:00.28* 354,840* 01060 ******** 5 CYGIPCS 12NOVyy:10:46:57.98 0:01:41.88* 178,301* 01062 ******** 0 BEAMA05M 07NOVyy:13:30:34.99 0:00:06.64 90,943* 5 IQBAM02D 06NOVyy:13:50:11.44 0:02:10.87* 34,038 JONCA04B 12NOVyy:15:43:33.43 0:03:32.57* 2,879 12NOVyy:15:55:19.91 0:01:10.59* 2,702 12NOVyy:16:10:50.76 0:01:14.38* 2,661 JONCA043 14NOVyy:12:03:07.41 0:00:24.55 126,664* 7 DIXPA02D 15NOVyy:10:46:48.50 0:01:17.18* 15,968 15NOVyy:13:30:36.48 0:01:14.50* 15,781 JSIEXTR 11NOVyy:14:33:57.06 0:00:03.56 48,436* WYKCH01D 11NOVyy:15:27:19.09 0:02:15.77* 25,010 12NOVyy:10:24:31.11 0:01:23.27* 26,935 01064 ******** 3 MANDA06L 04NOVyy:14:41:52.90 0:00:16.10 46,024* MANDA06M 04NOVyy:14:42:19.03 0:00:16.12 46,024* 01076 ******** 0 JERMI01L 11NOVyy:15:31:18.24 0:00:02.36 42,283* 11NOVyy:15:34:53.13 0:00:02.16 39,770* JERMI01M 11NOVyy:17:08:46.41 0:00:02.49 44,844* 11NOVyy:17:16:02.77 0:00:02.85 51,817* 11NOVyy:17:25:56.11 0:00:02.38 44,865* 11NOVyy:17:46:16.77 0:00:02.12 42,335* 11NOVyy:17:49:34.96 0:00:04.81 101,604* 11NOVyy:17:51:30.57 0:00:02.46 48,545* 11NOVyy:17:53:40.22 0:00:04.31 89,564* 11NOVyy:17:55:53.45 0:00:02.67 53,444* 12NOVyy:12:58:13.85 0:00:02.91 50,464* 7 FEESE01Y 07NOVyy:15:09:18.12 0:00:31.65 43,576* 07NOVyy:15:34:08.89 0:00:59.88 79,414* 15NOVyy:11:34:19.60 0:00:33.91 45,279* 01266 ******** 7 HENRO04Q 15NOVyy:11:00:52.65 0:00:05.13 95,660* GIS 00045 ******** 0 A02ICST3 12NOVyy:11:11:59.69 0:01:31.50* 9,099 MPIRSADT 08NOVyy:17:22:57.44 0:01:37.44* 5,808 TCWFAST$ 11NOVyy:11:23:34.38 0:00:17.46 99,448* 11NOVyy:11:50:11.47 0:00:19.64 156,990* TESTXCBK 14NOVyy:11:47:28.60 0:03:38.29* 10,763 TOPCDEVL 06NOVyy:17:18:56.79 0:07:28.57* 47,494* TOPCDEV2 08NOVyy:09:51:53.06 0:05:40.66* 148,789* 08NOVyy:11:42:22.55 0:01:40.63* 7,267 08NOVyy:13:41:37.00 0:01:38.81* 7,179 08NOVyy:13:49:04.83 0:01:33.66* 7,094 TOPCQAQA 12NOVyy:10:05:58.65 0:03:00.82* 14,794 14NOVyy:18:24:00.78 0:01:44.87* 25,197 TOPDDEV2 13NOVyy:10:25:47.61 0:20:52.34* 538,224* TOPDQAQA 06NOVyy:11:35:54.43 0:17:50.60* 1,154,523* WKBKVM82 04NOVyy:12:20:36.27 0:21:08.57* 225,024* WKBKVM83 04NOVyy:18:11:15.80 0:23:50.50* 230,790* WKBKVM84 11NOVyy:10:52:19.66 0:20:15.46* 220,572* WKBKVM85 11NOVyy:12:50:10.33 0:25:27.51* 220,572* Note: '*' Indicates that the data value is an outlier



 Figure 3-36.  Data Value Exception Detail report

The Data Value Exception report is dynamically built and does
not have a fixed format.  The first 'n' columns of the report
contain the sequence fields of the CA MICS file used for
analysis.  These fields are documented in the CA MICS Data
Dictionary.  The remaining elements are the ones that you
specify on the Data Clustering screen as clustering elements.
If these are CA MICS data elements, which is the typical
case, then their definitions and usage data can be located in
the CA MICS Data Dictionary as well.