Previous Topic: 3.1.3 UNIX Application InquiriesNext Topic: 3.1.4 UNIX Process Activity Analysis Inquiries


3.1.3.1 UNIX Application Performance Summary (AUMLS2)


The UNIX Application Performance Summary uses measurements
from the CA MICS AUMAPP file to display an overall view of
application performance in terms of throughput and
utilization by system for the date and/or time intervals you
request.
 
Each report provides metrics listed by application name.  A
separate report page is produced for each logical combination
of system, zone, and date/time interval, depending on the
report options you specify.  Measurements that allow an
overall view of application load, memory utilization, I/O
activity, and throughput are provided.  Wait statistics are
provided when you specify that the report be produced for the
DETAIL timespan.

 
The following MW OS Agent Analyzer data elements display:
 
  - AUMAPU   (application name)
  - AUMAPNUM (application number)
  - APPAVAPR (average processes active)
  - APPAVPRO (average processes alive)
  - APPDSKIO (physical I/Os)
  - APPLIOCT (logical I/Os)
  - APPPCCPU (total CPU use)
  - APPPCMPR (main memory use - private resident)
  - APPPCMRS (main memory use - resident)
  - APPPCSCP (% CPU wait time)
  - APPPCSDK (% disk I/O wait time)
  - APPPCSDR (% time directed to wait)
  - APPPCSIM (% software impede wait time)
  - APPPCSIP (% interprocess communication wait time)
  - APPPCSLN (% LAN I/O wait time)
  - APPPCSOT (% non-LAN, disk, terminal I/O wait time)
  - APPPCSWP (% memory wait time)
  - APPPCSYS (% CPU use for system processing)
  - APPPCUSR (% CPU use in user mode)
  - APPPKBRT (I/O transfer rate)
  - DURATION (duration)
 
For HP-UX B.10 systems, APPMEMPR (main memory use - private
resident) is not available.

For HP-UX A.09 systems, APPPKBCT (I/O transfer rate) and
APPMEMRS (memory use - resident) are not available.
 
For Solaris and AIX systems, the following data elements are
not available:
 
  - APPPCMPR (main memory use - private resident)
  - APPPCMRS (main memory use - resident)
  - APPPCSCP (% CPU wait time)
  - APPPCSDK (% disk I/O wait time)
  - APPPCSDR (% time directed to wait)
  - APPPCSIM (% software impede wait time)
  - APPPCSIP (% interprocess communication wait time)
  - APPPCSLN (% LAN I/O wait time)
  - APPPCSOT (% non-LAN, disk, terminal I/O wait time)
  - APPPCSWP (% memory wait time)

To produce the report:

  o Enter the CA MICS Workstation Facility (MWF)

  o Choose option 2, CA MICS Information Center Facility
    (MICF)

  o Choose option 2, Database Inquiries

  o Select AUMLS2, whose Catalog Group is Perform

  o Complete the MICF Execution panel

  o Complete the specification panel illustrated below
    (Descriptions of the fields follow the panel)
The result appears on your terminal and is illustrated at the
end of this section.

Note:  For this report, you can control the width of the
       report page (for example, to choose landscape versus
       portrait output) using the MICF Foreground Execution
       Parameters (MWF 2;0;2).  On the line
         Subset Display On ===>
       type Page.  Fill in a Page Width value that suits
       your reporting needs (80 to produce an 80 column
       report, for instance).
+----------------------------------------------------------------------+
|----------------- UNIX Application Performance Summary ---------------|
| Command ===>                                                         |
|                                                                      |
| Composing CA MICS Inquiry:                                           |
|                                                                      |
| Database ===> _________________________________________              |
| Cycle(s) ===> __ - __                                                |
| Timespan ===> ______ (DETAIL/DAYS/WEEKS/MONTHS)                      |
| Report by hour if timespan is DAYS or WEEKS ===> _ (Y/N)             |
| Generate a report for each value of Zone     ===> _ (Y/N)            |
|                                                                      |
| Data Selection:                                                      |
|                          Date Range 1         Date Range 2           |
|                     dd mmm yy   dd mmm yy   dd mmm yy   dd mmm yy    |
|   Date         ===> __ ___ __ - __ ___ __   __ ___ __ - __ ___ __    |
|   Hour         ===> __ - __    __ - __    __ - __                    |
|   Zone         ===> _ _ _ _ _ _ _ _ _                                |
|   Sysid        ===> ____ ____ ____ ____ ____ ____                    |
|                                                                      |
|   Application                                                        |
|   Name(AUMAPU) ===> ____________________   ____________________      |
|                     ____________________   ____________________      |
|                     ____________________   ____________________      |
|                                                                      |
+----------------------------------------------------------------------+

Data base - Required.  No default.  Specify up to six data
base unit IDs (the IDs of the CA MICS data base units from
which files are read).  Duplicates are not allowed.  If
CA MICS files exist in only one data base unit, this
parameter is set automatically.  To display a selection list
of valid data base unit IDs, specify ? (question mark).

Cycle(s) - Required.  Defaults to 01.  This is the cycle or
cycles of the specified time-span of the CA MICS files that
are used as input to the analysis.  Two data entry fields are
provided so you can specify a range of cycles.  The fields
can contain any numeric value between 0 and 99.  If you want
only a single cycle (such as cycle 01), specify the selected
cycle in the first entry field and leave the second field
blank.  Leading zeros are not required and are inserted
automatically if you supply a single-digit number (7 becomes
07).  If you specify a cycle range, you may specify it in
either ascending or descending order (for example, 01-05 or
05-01).

Time-span - Required.  Default varies by report time-span.
The time-span of the CA MICS data base from which the primary
input files are selected.  Required input file(s) must be
available at the specified time-span.

Report by hour - Required.  Defaults to Y.  At the DAYS and
WEEKS timespans, reports can be produced at an hourly level
or at the DAILY or WEEKLY levels.  If you specify Y (Yes) to
Report by hour, the data is summarized and displayed by hour
and separate reports are produced for each day or week.  If
you specify N (No) to Report by hour, the data is summarized
by day or week and a single report listing all days or weeks
is produced.
Generate a report for each value of Zone - Required.
Defaults to Y.  Specify Y (Yes) to generate reports for each
zone.  The nature and resource requirements of UNIX
processing often change from one zone to another (for
example, prime shift online demands versus production batch
requirements at non-prime shift periods).  Zone reporting
gives you the ability to display separate reports for each
observed zone.  If you specify N (No), the data is summarized
to the appropriate level and displayed on a single report.

Date - Optional.  No default.  Up to two date ranges in DD
MMM YY format.  The first value in each date range is the
starting date and the last value is the ending date.  The
ending date must be higher than the starting date.  The date
ranges should not overlap, but you can specify the higher
range before the lower range.  For example, a valid date
range specification is specifying date range 1 as
01 JAN 95 - 31 DEC 95 and specifying date range 2 as
01 JAN 94 - 31 DEC 94.  An input observation is selected if
its date value is greater than or equal to the starting date
and is less than or equal to the ending date of any specified
date range.

Hour - Optional.  No default.  0-23.  Up to three hour
ranges.  The first value is the starting hour and the last
value is the ending hour.  The ending hour must be higher
than the starting hour.  The hour ranges should not overlap,
but you can specify the higher range before the lower range.
For example, a valid hour range specification is 18 - 23 and
09 - 17.  An input observation is selected if its hour value
is greater than or equal to the starting hour and is less
than or equal to the ending hour of any specified hour range.

Zone - Optional.  No default.  1-character zone value from 1
to 9.  You can specify up to nine zone values.  An input
observation is selected if its zone value is equal to any of
the specified values.

Sysid - Optional.  No default.  1-4 character SYSID value.
You can specify up to six SYSIDs.  An input observation is
selected if its SYSID value is equal to any of the specified
values.

Application Name (AUMAPU) - Optional. No default. 1-20
character application name (AUMAPU). You can specify up to
six application names.  An input observation is selected if
its application name value is equal to any of the specified
values.

Detail Unix Application Performance Summary 09:46 Monday, June 23, 2008 CA MICS Data Integration Applications - a2 Reporting Period: 25SEP07:00:00 - 19MAY08:23:59 ------------------------------------------------ SYSID=CS00 OS=HP-UX DATE=02-10-14 ------------------------------------------------- (continued) Application | Application % CPU Use % CPU Use % CPU Use % Memory Use % Memory Use Time Name | Number Duration Total System Mode User Mode Private Resident Resident ----- ----------- | ----------- -------- --------- ----------- --------- ---------------- ---------------- 0:20 peoplesoft | 2 0:05:00 0.04 0.02 0.02 . 12.24 0:25 network | 4 0:05:00 0.01 0.01 0.00 . 0.26 0:25 other | 1 0:05:00 0.45 0.20 0.25 . 3.63 0:25 other_user_root | 6 0:05:00 4.97 2.82 2.15 . 2.22 0:25 peoplesoft | 2 0:05:00 0.04 0.02 0.02 . 12.24 0:30 network | 4 0:05:00 0.01 0.01 0.00 . 0.26 0:30 other | 1 0:05:00 0.34 0.14 0.20 . 3.62 0:30 other_user_root | 6 0:05:00 4.99 2.85 2.14 . 2.22 0:30 peoplesoft | 2 0:05:00 0.04 0.02 0.02 . 12.24 0:35 network | 4 0:05:00 0.01 0.01 0.00 . 0.26 0:35 other | 1 0:05:00 0.30 0.10 0.20 . 3.63 Application | Logical Physical I/O Transfer Avg Proc Avg Proc % Wait Time % Wait Time % Wait Time Time Name | I/Os I/Os Rate (KBytes) Alive Active CPU Disk I/Os Memory ----- ----------- | --------- ---------- ------------ -------- -------- ----------- ----------- ----------- 0:20 peoplesoft | 0 0 0.00 20 9.80 0.00 0.00 0.00 0:25 network | 0 0 0.00 27 5.00 0.00 0.00 0.00 0:25 other | 9000 420 0.00 41 3.30 0.00 0.00 0.00 0:25 other_user_root | 306300 1830 0.00 85 26.90 0.01 0.00 0.00 0:25 peoplesoft | 0 0 0.00 20 9.60 0.00 0.00 0.00 0:30 network | 0 60 0.00 27 5.40 0.00 0.00 0.00 0:30 other | 6900 420 0.00 41 3.70 0.00 0.00 0.00 0:30 other_user_root | 305700 1770 0.00 85 26.40 0.02 0.00 0.00 0:30 peoplesoft | 0 0 0.00 20 9.60 0.00 0.00 0.00 0:35 network | 0 0 0.00 27 4.70 0.00 0.00 0.00 0:35 other | 5400 390 0.00 40 3.40 0.06 0.00 0.00 Application | % Wait Time % Wait Time % Wait Time % Wait Time % Wait Time Time Name | Software Impedes Interproc Comm LAN I/Os Directed Other I/Os ----- ----------- | ---------------- -------------- ----------- ----------- ----------- 0:20 peoplesoft | 0.00 2.39 0.00 4.10 0.00 0:25 network | 0.00 0.00 0.00 66.66 0.00 0:25 other | 11.62 2.97 0.00 21.71 0.00 0:25 other_user_root | 0.36 0.74 0.00 28.42 0.19 0:25 peoplesoft | 0.00 2.39 0.00 4.10 0.00 0:30 network | 0.00 0.00 0.00 66.66 0.00 0:30 other | 11.62 2.97 0.00 21.71 0.00 0:30 other_user_root | 0.37 0.75 0.00 28.96 0.19 0:30 peoplesoft | 0.00 2.39 0.00 4.10 0.00 0:35 network | 0.00 0.00 0.00 66.66 0.00 0:35 other | 11.61 2.98 0.00 22.47 0.01