2. USAGE GUIDELINES › 2.3 Data Analysis Guidelines › 2.3.3 Analyzing Workload
2.3.3 Analyzing Workload
To plan for future growth, you must first analyze your
current workload. This requires breaking down the total work
into categories and developing a workload profile for each
category. This profile contains:
o transaction profile (number of functions)
o transaction volume
o resources required (real storage, DASD I/O, terminal
I/O)
The CA MICS Analyzer Option for CICS breaks down the workload
by summarizing detail transaction data by the application
unit IDs that you define at product installation time.
However, prior to using the CICS Application Unit Activity
File (CICCAU) for your workload analysis, you should be aware
of the factors that can affect the total transaction count in
CA MICS.
TRANSACTION COUNTS
The CA MICS Analyzer Option for CICS provides counts of CICS
transactions in the CICCSY, CICCSU, and CICCAU files for
various transaction types. These include short, medium,
long, and conversational transactions, as well as total
number of transactions.
Normally, one count is added to each of the above counts for
every detail transaction record input to the CA MICS Analyzer
Option for CICS. The transaction records are written for
each transaction execution. In an MRO/ISC environment, this
translates to multiple records for a routed transaction, as
each region produces a record for its execution of the
transaction. The CA MICS Analyzer Option for CICS currently
provides no facility to reduce the multiple records to a
single "unit of work." For conversational tasks, a
transaction record is usually written for each segment of the
conversation, thus resulting in multiple records for the
transaction. For CMF, multiple records are written for a
conversational task when the parameter CONV=YES is specified
in DFHMCT TYPE=RECORD macro.
There is an exception when a transaction record is not added
to any of the above transaction counts. This occurs when you
assign a TRANTYPE of "X" to a transaction using the CICS
relative longevity routine (CICRLRT). This exit allows you
to exclude certain transactions from the CA MICS response and
transaction distribution calculations, ensuring that the
response calculations are not skewed by transactions that may
have an abnormally long response time. Although the TRANTYPE
"X" transactions are not included in the total transaction
count, the CA MICS Analyzer Option for CICS does provide a
separate set of "excessive" counters for you to track these
transactions.
Note: The CPU time for the excessive transactions is included
in the total CPU time calculation.
Given the above conditions, you should consider the following
when analyzing the CICS transaction counts in the CICS files:
o The data elements presented by CA MICS no longer
represent the CICS task count, and should not be
analyzed for max task or max task within class
purposes.
o The transaction count data elements indicate relative
system load by transaction. An example of this is a
transaction that executes conversationally all day. It
may have very few CICS task counts, but it may also
account for a large percentage of the total CICS
resource use.
o Total transaction count does not include "excessive"
transactions as designated by your CICRLRT exit.
CICS FILE CONTROL CALLS
As part of the workload analysis, you are also estimating the
number of DASD I/Os that are performed by each category of
transactions. The CA MICS Analyzer Option for CICS provides
file access counts for you to analyze DASD usage. However,
CICS File Control calls do not correlate to the number of
physical I/Os performed for each file, as CICS only records
the number of logical requests made. If you have large VSAM
buffers allocated above the 16Mb line, there can be virtually
no physical I/Os performed for "get" type operations;
however, CICS will continue to count the file control calls.
On the other hand, a single insert operation to a VSAM file
with little free space can cause a CI or CA split, which may
result in many physical I/Os, but CICS will only show one
file control call in this case. Therefore, you should take
care not to use the number of file control calls as the
physical I/O count.
REPORTS
The CA MICS Analyzer Option for CICS provides you with
summary and management reports to analyze CICS workload. The
summary reports are produced by submitting a batch job after
the CA MICS daily update is completed. The management
reports are produced automatically by the CA MICS operational
jobs DAILY, WEEKLY, and MONTHLY. In addition, MICF inquiries
are provided for you to analyze CICS workload. You can
modify the inquiries to suit your data center's needs. The
MICF inquiries are executed on an ad hoc basis. See Chapter
3 of this guide for detailed descriptions and samples of the
following reports:
o Summary Reports
- Application Unit Summary Report
o Management Objective Reports
- Daily CICS Workload Report
- Weekly CICS Workload Report
- Monthly CICS Workload Report
o Graphic Inquiries
- CICCD1 - Daily CICS Workload Report
- CICCW1 - Weekly CICS Workload Report
- CICCM1 - Monthly CICS Workload Report
o Printer Graphic Inquiries
- CICPD1 - Daily CICS Workload Report
- CICPW1 - Weekly CICS Workload Report
- CICPM1 - Monthly CICS Workload Report
In addition to the above reports, you can code SAS programs
to retrieve workload-related data elements from the CA MICS
database.
FILE ELEMENT DESCRIPTION
------ ------- -----------
CICCAU CAUAVINC Average Input Character Traffic
CICCAU CAUAVMEM Average Transaction Memory Used
CICCAU CAUAVOPS Average number of CICS Calls
CICCAU CAUAVOTC Average Output Character Traffic
CICCAU CAUAVTRT Average Transaction CPU Time
CICCAU CAUCINP Input Characters - Primary Facility
CICCAU CAUCOUTP Output Characters - Primary Facility
CICCAU CAUCINS Input Characters - Secondary Facility
CICCAU CAUCOUTS Output Characters -Secondary Facility
CICCAU CAUCPRTM Task CPU Real Time
CICCAU CAUCPUTM Task CPU Time (elapsed)
CICCAU CAUDLIWT DL/I Call Elapsed Time (ASG-TMON)
CICCAU CAUDLICC DL/I Call Count (ASG-TMON)
CICCAU CAUFCTOT Total File Requests
CICCAU CAUJCOPS Number of Journal Control Calls
CICCAU CAUMINP Input Messages - Primary Facility
CICCAU CAUMINS Input Messages - Secondary Facility
CICCAU CAUMOUTP Output Messages - Primary Facility
CICCAU CAUMOUTS Output Messages - Secondary Facility
CICCAU CAULTRN Long Transaction Count
CICCAU CAUMTRN Medium Transaction Count
CICCAU CAUPCOPS Number of Program Control Calls
CICCAU CAUSCOPS Number of CICS Storage Control Calls
CICCAU CAUSIOCT Access Method Calls
CICCAU CAUSPOPS Number of CICS Synch Point Calls
CICCAU CAUSTOTM Storage Occupancy Time
CICCAU CAUSTRN Short Transaction Count
CICCAU CAUTDGET Transient Data Gets
CICCAU CAUTDOPS Number of CICS Transient Data Calls
CICCAU CAUTDPUT Transient Data Puts
CICCAU CAUTDPRG Transient Data Purges
CICCAU CAUTRANS Transactions processed
CICCAU CAUTSGET Temporary Storage Gets
CICCAU CAUTSOPS Number of CICS Temporary Storage Calls
CICCAU CAUTSPTA Temporary Storage Puts to AUX
CICCAU CAUTSPTM Temporary Storage Puts to Main
