WEBSL1 - WEB Performance Summary
The WEB Performance Summary uses measurements from the WebSphere Performance File (WEBWPR).
micsrm140
The WEB Performance Summary displays an overall view of the utilization and activity for each of the selected Web Names for the date and/or time ranges you select.
Each report produced displays categorized information on utilization, caching, and errors. The report categories and element labels are listed on the left side of the report pages. Individual columns on the report represent the element's value for the selected granularity level (hour, interval, or date) as denoted above the columns. The last column on the report represents the percent increase or decrease over the time periods represented on the report page.
The following table displays the relationship between report labels, originating file, and
MICS database
source elements for each performance category.Report Label | File | Element |
AVG BYTES PER CACHE HIT | WEBWPR | WPRAVBCH |
% OF TOT REQ MET BY CACHE | WEBWPR | WPRPCCAH |
AVG BYTES SENT PER SECOND | WEBWPR | WPRBYSPS |
MAX BYTES SENT PER SECOND | WEBWPR | WPRMXBSS |
AVG BYTES REC. PER SECOND | WEBWPR | WPRBYRPS |
MAX BYTES REC. PER SECOND | WEBWPR | WPRMXBRS |
MAX THREADS DEFINED | WEBWPR | WPRMXTRD |
MAX THREADS USED | WEBWPR | WPRMXTRU |
THREADS USED | WEBWPR | WPRTRDCT |
REQUESTS RECEIVED | WEBWPR | WPRREQR |
REQUESTS DISCARDED | WEBWPR | WPRREQDC |
RESPONSES SENT | WEBWPR | WPRRSPS |
RESPONSES DISCARDED | WEBWPR | WPRRSPD |
BYTES RECEIVED | WEBWPR | WPRBYTR |
BYTES SENT | WEBWPR | WPRBYTS |
KBYTES READ FROM CACHE | WEBWPR | WPRKBCAC |
CACHE HITS | WEBWPR | WPRCACHT |
BYTES OF CACHE RAM IN USE | WEBWPR | WPRCACRM |
ERROR LEVEL 200 RESPONSES | WEBWPR | WPRL200R |
ERROR LEVEL 300 RESPONSES | WEBWPR | WPRL300R |
ERROR LEVEL 400 RESPONSES | WEBWPR | WPRL400R |
ERROR LEVEL 500 RESPONSES | WEBWPR | WPRL500R |
TOTAL ERROR RESPONSES | WEBWPR | WPRERRCT |
Note:
The label associated to the field DATE in the column titles will vary based on timespan used.To produce the report, follow these steps:
- Enter theMICS Workstation Facility(MWF)
- Choose option 2,MICS Information Center Facility(MICF)
- Choose option 2, Database Inquiries
- Select WEBSL1, Catalog Group: PERFORM
- Complete the MICF Execution panel
- Complete the specification panel illustrated below (Descriptions of the fields follow the panel)The result displays on your terminal.
+----------------------------------------------------------------------+ |------------------------WEB Performance Summary ----------------------| | Command ===> | | | | Composing Inquiry: WEBSL1 - WEB Performance Summary | | | | Database ===> _________________________________________ | | Cycle(s) ===> __ - __ | | Time-span ===> ______ (DETAIL/DAYS/WEEKS/MONTHS) | | Report by hour if time-span is DAYS or WEEKS ===> _ (Y/N) | | Generate a report for each value of Zone ===> _ (Y/N) | | | | Data Selection: | | dd mmm yy dd mmm yy dd mmm yy dd mmm yy | | Date Ranges ===> __ ___ __ - __ ___ __ __ ___ __ - __ ___ __ | | Hour ===> __ - __ __ - __ __ - __ | | Zone ===> _ _ _ _ _ _ _ _ _ | | Sysid ===> ____ ____ ____ ____ ____ ____ | | WEB Short Names(WEBSNAME) ===> ____ ____ ____ ____ ____ ____ | | WEB Name ===> _____________________ _____________________ | | _____________________ _____________________ | | WEB Group(WEBGROUP) ===> ________ ________ ________ ________ | | | +----------------------------------------------------------------------+
Parameter Specifications
Required Parameters
The following parameters require specification for the inquiry to execute.
DATABASE.
Default: None
Specify up to six database unit IDs (the IDs of the
MICS database
units from which files are read). If MICS
files exist in only one database unit, this parameter is set automatically.
To display a selection list of valid database unit IDs, specify ? (question mark). Duplicates IDs are not allowed.
CYCLE(S).
Default: 01
This is the cycle or cycles of the specified timespan of the
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).TIMESPAN.
Default: Varies by report
The timespan of the
MICS database
from which the primary input files are selected. Required input file(s) must be available at the specified timespan. (e.g., DETAIL, DAYS, WEEKS, MONTHS, YEARS)Report By Hour.
Default: Y At the DAYS and WEEKS timespans, reports can be produced at an hourly, DAILY, or WEEKLY level.
Y
(Yes) to Report by HOUR. The data is summarized and displayed by hour and separate reports are produced for each day or week.
N
(No) to NOT 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.
Default: Y
Y
(Yes) to generate reports for each ZONE.
N
(No) to NOT generate reports for each ZONE.
The nature and resource requirements of 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.
Optional Parameters
The following parameters do not require specification for the inquiry to execute, they are optional.
DATE RANGES.
Default: None
Specify 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:
date range 1: 01 JAN 01 - 31 DEC 01
date range 2: 01 JAN 99 - 31 DEC 99
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.
Default: None
Specify up to hour ranges of the form mm - nn, where mm and nn are two digit numbers between 00 and 23, inclusive.
mm
range starting hou
nn
range 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 09-17 02-04
An input observation is selected if its hour value is greater than or equal to the starting hour and less than or equal to the ending hour of any specified hour range.
ZONE.
Default: None Specify up to six ZONE values.
Each ZONE a 1 byte character field.
Duplicates are not allowed.
Using ZONEs you can restrict the inquiry analysis to only those ZONE values specified.
SYSID.
Default: None Specify up to six SYSIDs.
Each SYSID a 1-4 byte character field.
Duplicates are not allowed.
Using SYSIDs you can restrict the inquiry analysis to only those SYSID values specified.
WEB SHORT NAMES (WEBSNAME).
Default: None Specify up to six Web Short Names.
Each Web Short Name is a 1-4 byte character field.
Duplicates are not allowed.
Using WEBSNAMEs you can restrict the inquiry analysis to only those WEBSNAME values specified.
WEB NAME (WEBNAME)
Default: None Specify up to four Web Names.
Each Web Name is a 1-20 byte character field.
Duplicates are not allowed.
Using WEBNAMEs you can restrict the inquiry analysis to only those WEBNAME values specified.
WEB G ROUP (WEBGROUP)
Default: None
Specify up to four Web Groups.
Each Web Group is a 1-8 byte character field.
Duplicates are not allowed.
Using WEBGROUPs you can restrict the inquiry analysis to only those WEBGROUP values specified.
BroadcomMICSWebSphere Analyzer DETAIL WEB PERFORMANCE SUMMARY FOR ZONE = 1 SYSTEM = XAL1 WEB NAME = HELP DESK RUNDATE = Sep 10, 2005 ---------------------------------------------------------------------------- | | | INTVL-DAY (HR:MM-DD): 11:16-26 12:58-26 16:11-26 16:58-26 CHANGE % | | | |--------------------------------------------------------------------------| | | | WEBSPHERE ACTIVITY | | ------------------ | | | | BYTES SENT 42730 78002 18145 94083 120.18 % | | AVG BYTES SENT PER SECOND 1 13 2 34 3300.00 % | | MAX BYTES SENT PER SECOND 1 13 2 34 3300.00 % | | BYTES RECEIVED 3334 6107 1762 5525 65.72 % | | AVG BYTES REC. PER SECOND 0 1 0 2 N.A. | | MAX BYTES REC. PER SECOND 0 1 0 2 N.A. | | THREADS USED 2 2 1 1 -50.00 % | | MAX THREADS DEFINED 50 50 50 50 --- | | MAX THREADS USED 2 2 1 1 -50.00 % | | REQUESTS RECEIVED 8 15 4 13 62.50 % | | REQUESTS DISCARDED 0 0 0 0 N.A. | | RESPONSES SENT 10 15 4 13 30.00 % | | RESPONSES DISCARDED 0 0 0 0 N.A. | | | |--------------------------------------------------------------------------| | | | WEBSPHERE CACHE STATS | | --------------------- | | | | CACHE HITS 5 8 2 6 20.00 % | | % TOTAL REQ MET BY CACHE 62.50% 53.33% 50.00% 46.15% -26.16 % | | AVG BYTES PER CACHE HIT 175 81 348 79 -54.86 % | | KBYTES READ FROM CACHE 19 26 5 26 36.84 % | | BYTES OF CACHE RAM IN USE 42090 42090 42090 42090 --- | | | |--------------------------------------------------------------------------| | | | WEBSPHERE ERRORS | | ---------------- | | | | ERROR LEVEL 200 RESPONSES 7 12 3 13 85.71 % | | ERROR LEVEL 300 RESPONSES 1 3 1 0 N.A. | | ERROR LEVEL 400 RESPONSES 2 0 0 0 N.A. | | ERROR LEVEL 500 RESPONSES 0 0 0 0 N.A. | | TOTAL ERROR RESPONSES 10 15 4 13 30.00 % | | | ----------------------------------------------------------------------------