CA MICS Analyzer Option for IDMS (IDM) Queries › IDMT10 - IDMS Daily Top Ten Programs Executed › Overview

Overview

The IDMT10 query produces charts that identify the programs that are the most frequently executed by IDMS transactions. The top nn programs are targeted, the default is10. These charts display resource and performance-related metrics for these highly used programs.

The query generates two CSV output files that identify:

• The top 10 programs executed at the IDMS region level
• The top 10 programs executed at the z/OS SYSID level where the transaction data from multiple IDMS regions is consolidated

The data extract CSVs generated by the IDMT10 query are:

• Daily Top 10 IDMS Programs by Region
• Daily Top 10 IDMS Programs by SYSID

Each data extract generates the following three chart views:

• Top 10 Programs Transaction Count
• Top 10 Programs CPU Time
• Top 10 Programs Response Time

By default the query is executed against:

• DAYS timespan HARCPU file (to obtain the CPC identification for each SYSID)
• DAYS timespan IDMSUA file (to obtain the IDMS transaction information)

Each X axis value represents one of the top 10 program names. Data for the entire day is summarized to determine the most frequently executed program.

Considerations:

• By default, the SUAPGM (Batch/CICS/DC Program Name) data element is not located in the DAYS timespan IDMSUA file .

  However, by convention, the sharedprefix.MICS.PARMS(IDMACRT) routine typically assigns SUAPGM to one of the IDMACTn Account Code summarization keys.

• You might see ‘*BLANKS*’ as the name of one of the 10 most-executed programs. The IDMS transaction records sometimes contain blanks or binary zeros in the program name field. During the query execution, the query code replaces any blank or binary zero program names with the value ‘*BLANKS*’ before it determines the 10 most-executed programs.

Chart view #1

View #1 uses pie charts to show the 10 most frequently executed programs. The number of transactions that executed the program determines the size of each pie slice.

The first chart sample (shown previously) is an example of the charts produced by View #1 from the "by Region" data extract CSV.

The chart sample shows IDMS region CV02 which is executing on SYSID CA31, running on an IBM 2817-615 (z196 CPC with 15 subcapacity CP engines). Notice that the two most frequently executed programs were ZWHLNZRM and ISWXNHGI. The two programs represent over 60% of the programs that were executed by transactions for this IDMS region (33.1% ZWHLNZRM and 29.5% for ISWXNHGI).

Chart View #2

View #2 uses stacked vertical bars to show:

• The CP processor CPU time
• CP processor CPU time that was eligible to run on a zIIP engine (but did not)
• Normalized zIIP processor CPU time used by each of the top 10 programs

Also, a horizontal line displays the transaction count for each of the programs.

The second chart sample (shown previously) is an example of the charts produced by View #2 from the "by Region" data extract CSV. It shows the top 10 programs executed by IDMS region CV02. From this chart sample you can see:

• About 1/3rd of the CPU time consumed by the most frequently executed program, ZWHLNZRM, (the right-most program on the X axis), executed on a zIIP processor engine (light blue bar segment).
• About 2/3rd of the CPU time was consumed on standard CP processor engines (dark blue bar segment)
• Only a small amount of zIIP-eligible CPU time was processed on standard CP engines (red bar segment).

Note: The second most frequently executed program, ISWXNHGI (fourth program from the left on the X axis) used much less CPU time than program ZWHLNZRM, even though the number of transactions executed was similar (3,446 for ISWXNGHI and 3,860 for ZWHLNZRM). This means that the average CPU time expended for each execution of ZWHLNZRMI was much greater than for ISWXNGHI.

Chart view #3

View #3 uses stacked vertical bars to show the number SHORT, MEDIUM, and LONG transactions that executed each of the top 10 programs. In addition, the average SHORT and MEDIUM transaction response times are displayed using horizontal lines.

The third chart sample (shown previously) is an example of the charts produced by View #3 from the "by Region" data extract CSV. It shows the transaction counts and response times for the same IDMS region that is displayed in the first chart. Examining ZWHLNZRM, the most frequently executed program (the rightmost program on the X axis), you can see:

• About 1/3rd of the transactions that executed this program were MEDIUM (red bar segment) and 2/3rd of the transactions were SHORT (dark blue bar segment).
• The average transaction response times were:
  • SHORT transactions - about 0.02 seconds
  • MEDIUM transactions - about 0.30 seconds

Important! Read the Query Defaults topic for information about the updates you might have to make to execute this query successfully in your environment.