|
|
|
The Monthly CICS Workload Ranking inquiry produces tabular
reports which identifies the top 10 CICS applications in
transaction volume.
REPORT FORMAT:
This inquiry produces a tabular report which contains a
summary section and a ranking section. The summary section
shows the total workload and the peak hour workload. The
ranking section identifies the 10 applications with the
highest transaction volume and provides other pertinent
information such as response time, CPU time, data base calls,
character traffic, and storage usage.
A sample output of this inquiry is shown in Figure 3-28.
Each field in this report is described below:
SYSTEM SUMMARY:
# REGIONS: Total number of SYSID/CICSID combinations found
in input.
TRANS: The total number of transactions processed. For
TYPE=ALL, this number excludes transaction type X
(TRANTYPE=X as assigned by the CICRLRT exit).
%SHORT: The percentage of short transactions processed.
%MED: The percentage of medium transactions processed.
%LONG: The percentage of long transactions processed.
AVG RESP: The average response time for the transactions
processed. For TYPE=ALL, this number excludes
transaction type X (TRANTYPE=X as assigned by the
CICRLRT exit).
TOTAL CPU: The total TCB CPU time consumed by all
transactions, excluding transaction type X.
PEAK HOUR: The hour during which CICS processed the highest
number of transactions.
PEAK TRAN: The total number of transactions processed during
peak hour, excluding transaction type X.
PEAK CPU: The total TCB CPU time consumed during peak hour.
PEAK RESP: The peak average hourly response time provided by
CICS.
RANKING SECTION:
RANK: The ranking, number 1 to 10, in transaction
volume.
APPL: Application identification.
TRANS: The total number of transactions processed for
the application.
AVG RESP: The average response time for all transactions
processed for this application.
TOT CPU: The total TCB CPU time consumed by this
application.
FC CALLS: The total number of file control calls issued by
this application.
DBMS CALLS: The total number of data base calls (DB2 and IMS)
issued by this application.
TOT CHARS: The total number of input and output characters
generated by this application.
MAX The maximum amount (in 1024 bytes) of terminal
STORAGE: and user storage used by this application.
AVERAGE The average TCB CPU per transaction consumed by
CPU: this application.
AVERAGE The average number of file control calls per
FC CALLS: transaction issued by this application.
AVERAGE The average number of data base (DB2 and IMS)
DBMS CALLS: calls per transaction issued by this application.
AVERAGE The average number of input and out characters
CHAR: per transaction generated by this application.
AVERAGE The average amount of dynamic storage (terminal
STORAGE: and user) per transaction consumed by this
application.
% ABND: The percentage of transactions that abended for
this application.
INQUIRY ID:
CICLMH (tabular report)
DATA SOURCE (file/timespan):
CICCAU01 in the DAYS timespan.
If the CICCAU (CICS Application Unit Activity) file is
not active, the CICCSU (CICS User Activity) file will be
used for reporting. The variable CICACT2 will be used
in place of the variable CICAPU.
One graph produced for each date and each combination of
SYSID/CICSID.
DATA ELEMENTS USED:
CICAPU - CICS Application Unit ID
CICSID - CICS System Identifier
CAUABEND - Abnormal Termination Occurrences
CAUCTRN - Conv. Transactions Processed
CAUETRN - Excluded Transactions
CAUDLICC - Number of CICS DL/I Calls
CAUFCOPS - Number of CICS File Control Calls
CAUINCH - Input Message Character Traffic
CAULTRN - Long Transactions Processed
CAUMEMRC - Memory Usage Running Count
CSUMTRN - Medium Transactions Processed
CAUMXMEM - Maximum Transaction Storage Used
CAUOUTCH - Output Message Character Traffic
CAUCPUTM - Task CPU Time
CAUSQLTO - Total number of SQL Calls
CSUSTRN - Short Transactions Processed
CAUTRANS - Transactions Processed
CAUTRSTM - Transaction Response Time Total
DAY - Day of Month
MONTH - Month of Year
YEAR - Year of Century
ZONE - Time Zone
SYSID - System Identifier
CALCULATIONS:
Average response time = CAUTRSTM/CAUTRANS
Average character = SUM(CAUINCH,CAUOUTCH)/
SUM(CAUTRANS,CAUETRN)
Average CPU time = CAUCPUTM/CAUTRANS
Average DBMS calls = SUM(CAUDLICC,CAUSQLTO,CICPCT01)/
SUM(CAUTRANS,CAUETRN)
Average file control calls = CAUFCOPS/
SUM(CAUTRANS,CAUETRN)
Average storage = CAUMEMRC/SUM(CAUTRANS,CAUETRN)
Percent abend = CAUABEND/CAUTRANS
Percent conv. = CAUCTRN/CAUTRANS
Percent long = CAULTRN/CAUTRANS
Percent medium= CAUMTRN/CAUTRANS
Percent short = CAUSTRN/CAUTRANS
EXECUTION-TIME PARAMETERS:
UNIT - Select one or more CA MICS data base units by
entering the data base IDs. Enter multiple IDs
with a blank following each ID value.
CYCLE - Optionally, define CA MICS input file cycle
range.
For this inquiry, the default is the 01 cycle.
SYSID - Optionally, specify the SYSID to be reported.
If no value is specified, the value *ALL is
used. It causes all SYSIDs found in input to
be summarized together.
CICSID - Optionally, specify the CICSID to be reported.
If no value is specified, the value *ALL is
used which causes all CICSIDs found in input to
be summarized together.
MONTH - Optionally, enter the month (mm) and year (yy)
to be reported.
For this inquiry, the default is previous
month.
ZONE - Optionally, select one or more CA MICS time
zones. Valid values are numbers 1 through 9.
TRAN - Optionally, select the type of transaction to
be ranked. The response types are TOTAL,
SHORT, MED, LONG, or CONV. The default is
TOTAL.
FILE ID- Optionally, select the CICCSU file as input
when the CICCAU file is active. If you specify
this parameter, then you must also specify the
next parameter to indicate which account code
(CICACT1-CICACT9) identifies your CICS
application.
CICAPU - Optionally, replace CICAPU with any of the
CICACTx data elements, where x is 1 to 9. This
parameter must be specified in conjunction with
FILE ID.
USER EXITS:
If the MICF execution-time parameters are insufficient
to select the data you need, you can invoke one of the
following global exits to further manipulate the input
file. Additionally, you can override the global exit
definitions in MICF using independent source statements.
For detailed information on coding the exits, refer to
Section 3.2 of this guide.
The global exits are defined by macros in the source
module CICRPTGL in sharedprefix.MICS.SOURCE. The
following exits are available to this inquiry:
%GAPPL - Define your CICS application based on any
variable in the input file. The default is
CICAPU.
%GCIC - Select CICSIDs for report.
%GCNTR - Assign value to the variable CENTER which
defines the logical grouping of SYSIDs.
CENTER is set to SYSID by default.
%GSYS - Select SYSIDs for report.
In addition to the above exits, the module CICRPTGL also
contains macro variables which set default values for
service level objectives. Please see Section 3.2 to
override the default values.
MONTHLY CICS WORKLOAD RANKING REPORT your_company_name FOR AUGUST, 1991 INQUIRY: CICLMH RUN DATE: 06SEP91 SYSTEM SUMMARY: 7 REGIONS % % % % AVG TRANS/ -------- PEAK ACTIVITY -------- # TRANSACTIONS SHORT MED LONG CONV RESP SEC HOUR TRANS TRAN/SEC RESP 644,528 56.3 0.0 36.0 7.7 0.32 1.6 9 75,037 3.0 0.15 ** TOP 10 APPLICATIONS IN TOTAL TRANSACTION VOLUME TOTAL AVG TOT FILE CNTL DBMS TOT CHARS MAX -------------- AVERAGES -------------- % RANK APPL TRANS RESP CPU CALLS CALLS (000) STORAGE CPU FC CL DBMS CL CHAR STORAGE ABND 1 TOSC 344,062 0.13 0:11 42 0 416132 8K 0.00 0 0 1209 8K 0 2 CRSR 29,214 0.02 0:01 0 0 0 11K 0.00 0 0 0 11K 0 3 CSNE 26,610 0.02 0:01 0 0 45 33K 0.00 0 0 2 30K 0 4 PUBC 24,221 0.15 0:04 48134 0 26592 23K 0.01 2 0 1098 28K 0 5 ISHD 23,006 0.62 0:12 29458 0 29997 184K 0.03 1 0 1304 279K 0 6 CSGM 17,561 0.03 0:01 84 0 16785 8K 0.00 0 0 956 9K 0 7 CATD 17,344 0.09 0:02 0 0 0 23K 0.01 0 0 0 300K 0 8 DATA 16,126 0.15 0:01 6900 0 10762 1448K 0.00 0 0 667 20K 0 9 PUSC 15,199 0.04 0:02 14299 0 15168 92K 0.01 1 0 998 36K 0 10 PIBC 10,675 0.13 0:02 17170 0 11801 13K 0.01 2 0 1105 25K 0
Figure 3-28. Monthly CICS Workload Ranking Report Sample Output
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |