Overview

The Overview page displays information about the monitoring process, and key global statistics about the monitored application. Use these statistics to determine the next most logical page to view in your analysis.

Contents:

Note: The Overview page opens as the default page when you open the Analysis window.


Following the overview contents, log contents are displayed. CA Mainframe Application Tuner supports three log types as follows:

Overview Page Fields

The Overview page contains the following fields:

Job Information

  • Jobname
    The name of the job that was monitored.

  • Stepname
    One of the following:

    • The step name on the EXEC statement that invoked the program (if no cataloged procedure is used).

    • The name of the step that invoked the procedure (if a cataloged procedure is used).

  • Procstep
    The procedure step name (if a cataloged procedure is used).

  • Program
    The name of the program on the EXEC statement of the JCL of the job that was monitored.

  • ASID
    Decimal address space identifier of the job that was monitored.

  • (HEX)
    Hexadecimal address space identifier of the job that was monitored.

  • User ID
    Identifier of the user who requested the sampling. If the monitor was invoked by a batch job using TUNCALL, this field displays the name of the batch job.

  • Job ID
    JES job identifier of the job that was monitored.

  • CICS Level
    Release level of the CICS system on which the sampling was done. This field displays **N/A** unless CICS was detected for the job being monitored.

  • DB2 Level
    Release level of the DB2 system used by the job. This field displays **N/A** unless DB2 was detected for the job being monitored.

  • IMS Level
    Release level of the IMS system used by the job. This field displays **N/A** unless IMS was detected for the job being monitored.

  • MQS Level
    Release level of the MQSeries system used by the job. This field displays **N/A** unless MQSeries was detected for the job being monitored.

  • SAP Level
    Release level of the SAP system used by the job. This field displays **N/A** unless SAP was detected for the job being monitored.

  • USS Level
    Release level of Unix System Services used by the job. This field displays **N/A** unless USS was detected for the job being monitored.

  • WAS Level
    Release level of the WebSphere Application Server used by the job. This field displays **N/A** unless WAS was detected for the job being monitored.

  • < Rgn Lim
    The amount of private storage (region) available below 16 megabytes.

  • > Rgn Lim
    The amount of private storage (region) available above 16 megabytes.

  • Rgn Request
    The amount of private storage (region) requested by the job.

  • Dynamic Linklist
    The name of the user-specified dynamic linklist, if using a linklist other than that specified during IPL.

Job Statistics

  • TCB Time
    Amount of CPU time used by execution of code in task mode during the monitored period. It is obtained from the ASCB.

  • SRB Time
    Amount of CPU time used by execution of code in SRB mode during the monitored period. It is obtained from the ASCB.

  • ECPU Time
    The amount of CPU time used within this address space in HH:MM:SS.TH format.

  • zAAP Time
    The amount of CPU time used by this address space in a zSeries Application Assist Processor (zAAP) in HH:MM:SS.TH format.

  • Elig zAAP
    The total time that there was Java Timework eligible to run on a zSeries Application Assist Processor (zAAP). Within a particular application, some work might be Java and the JVM has designated the work as zAAP-eligible, while other work might be non-Java, or might be Java work that was not marked zAAP-eligible by the JVM. The zAAP-eligible work can be switched to a zAAP for processing, and when the work that is not zAAP-eligible is ready to execute, this work would execute on a standard CP. A Switch Service is in place to work with the z/OS Dispatcher, managing the dispatching of zAAP eligible work between the standard CPs and the zAAP Engines.
    This field can help identify opportunities where a zAPP processor would benefit processing and identify issues with available zAPP processors not being fully utilized. New zAAP users should refer to the JVM Startup Options for zAAPs such as-Xifa: as well as new parameters in the IEAOPTxx of SYS1.PARMLIB such as IFACrossover.

  • zIIP Time
    The amount of CPU time that was spent actually executing on an Integrated Information Processor (zIIP) in HH:MM:SS.TH format.

  • Elig zIIP
    The total time that there was work Timeeligible to run on a zSeries Integrated Information Processor (zIIP) engine(s). Note that only enclave SRB work is eligible to run on the zIIP. DB2 and IPSEC are two of the initial exploiters.
    Within a particular application or subsystem only the Enclave SRB work is designated as zIIP-eligible. A Switch Service is in place to work with the z/OS Dispatcher, managing the dispatching of zIIP eligible work between the standard CPs and the zIIP Engines.
    This field can help identify opportunities where a zIIP processor would benefit processing and identify issues with available zIIP processors not being fully utilized. There is one external tuning option, zIIPAWMT, which controls the 'needs help' dispatcher. Also note APAR OA20045 that enables the IIPHONORPRIORITY=Yes/No Specification for z/OS 1.8.

  • Swapped Out
    The amount of time the address space was observed to be swapped out during the measurement in
    HH:MM:SS.TH format.

  • Non Disp
    The amount of time the address space was observed to be non-dispatchable (the ASCB non-dispatchability flags were on) during the measurement in HH:MM:SS.TH format.

  • LPAR/DIS
    The amount of time the address Delayspace was observed to be delayed because of either LPAR delay or other disabled work on the processor during the time of the measurement in HH:MM:SS.TH format.

  • Wait Time
    The amount of time that the monitored application was in a wait.

  • CPU Svc Units
    CPU Service units, which are an interval of CPU time normalized by a CPU processor-specific adjustment rate.

  • EXCP count
    Number of input/output operations for the job-step during the monitored period. This number includes I/O counts that are not reflected in the I/O counts at the DD name level. Refer to the SMF_Discussion for additional information.

  • EXCP rate
    Number of I/O operations per second for the job during the monitored period.

  • < Rgn Used
    High-water amount of virtual HWMstorage below the 16 MB line used by the job being monitored.
    This value might actually be larger than the requested size if modified by products or SMF exits.

  • > Rgn Used
    High-water amount of virtual HWMstorage above the 16 MB line used by the job being monitored.
    This value might actually be larger than the requested size if modified by products or SMF exits.

  • Page-ins
    Number of page-in operations for the job during the monitored period. A high value in this field may indicate job delays.

  • Page-in Rate
    Number of paging operations per second for the job during the monitored period.
    A high rate can indicate job delay due to storage constraints. When reference is made to a page due to storage constraints. When reference is made to a page of virtual storage that does not appear in central storage, the page is brought in from DASD or expanded storage to replace a page in central storage. The newly referenced page is said to have been "paged in". It is the page-in (not page-out) rate that is of primary concern because page-in activity occurs synchronously (for example, the task stops until the page fault is resolved).

Monitor Statistics

  • Start date
    The date the monitor started.

  • Start time
    Time the monitor started.

  • Duration
    Amount of time the monitor ran (in the format HH:MM:SS).

  • Observations
    An observation is the number of times that CA MAT will examine the activity of the address space to be measured. Click here for more details.

  • Observations Final Rate
    The Final observation rate that is calculated by CA MAT. This rate is the rate that was in effect at the actual end of the measurement, regardless of whether the rate may have changed from the initially calculated value.
    Click here for more details.

  • Observations Requested
    The number of observations that are requested by the user.
    Observations: The actual number of observations that are made by CA MAT.

  • Samples
    A sample within CA MAT reflects the activity of a TCB during an observation. Click here for more details.

  • Samples: Used
    The number of samples that are selected from those collected during the monitored period in accordance with the analysis mode selected.
    For analyze NORMAL mode, Swapped and ProcDly samples are omitted.
    For analyze ACTIVE mode, only Active samples are considered. All others are omitted.
    For analyze WAIT mode, only Wait samples are considered. All others are omitted.
    For analyze ALL mode, no samples are omitted.
    A significant difference may be noted when STEP level sampling is conducted as many samples are discarded.

  • Samples: % Active
    The percentage of samples used Active that were recorded when the application was actively using CPU.

  • Samples: % Wait
    The percentage of samples used Wait that were recorded when the application was not using CPU and was waiting on a resource.

  • Avg TCBs Act
    The average number of TCBs that were actively using the CPU during an observation.
    This value can be from 0 up to the number of online CPUs.

  • > CMN HWM
    The high-water-mark amount of Used common (ECSA) storage used by CA MAT to measure the job.
    This value can be used for planning purposes on setting the maximum active number of monitors allowed.
    This value might actually be larger than the requested size if modified by products or SMF exits.

System Information

  • Sys Name
    The eight-character system name identifier for the z/OS image on which the sampling was performed.

  • SMFID
    The four-character System Management Facility identifier for the z/OS image on which the sampling was performed.

  • OS FMID
    The release level of the MVS system where the target job executed.

  • OS Name
    The name of the operating system

  • OS Level
    The release level of the operating system

  • OS Owner
    The name of the operating system owner

  • CPU Model
    The CPU model number of the system on which the sampling was performed.

  • CPU Version
    The CPU version of the system on which the sampling was performed

  • CPU Serial
    The serial number of the processor on which the sampling was performed

  • CPU Adj Rate
    The processor-specific adjustment rate that is used in the calculation of CPU service units. This value is based on the number of instructions per CPU second for a given processor.

  • Working Set Size Chart
    The Working Set Size Chart displays the average frame count usage over time. The total monitor period is divided into 50 equal intervals. Each '+' on the chart represents the average frame count for an interval.
    The chart contains ten rows whose range is determined by the minimum and maximum average frame count that is used for the monitored period. The number of frames per row is calculated as:
    (Max Avg. Frame Count - Min Avg. Frame Count)/9

Resource Demand Chart

This section of the Monitor Overview panel contains a chart depicting the approximate percentage of time the application spent either running on a CPU or being delayed for data over the life of the monitor run.

The total monitor run is split into 50 equal periods, each period being 2 percent of the total run. The activity is summarized into each slot by resource type. In this way, you see an overview of the resource demands during the life of the monitor run.

The following information is shown:

  • Database ID
    Database ID which uniquely identifies the resource being reported.

  • TYPE
    The type of resource:

  • CPU
    Application active on processor for a task resource

  • I/O
    Application delayed for I/O on ddname resource

  • DB2
    Application delayed for DB2 statement on DBRM resource

  • MQS
    Application delayed for MQSeries resources

  • SAP
    Application delayed for SAP resources

  • ADA
    Application delayed for Adabas statement

  • DCM
    Application delayed for Datacom statement

  • IMS
    Application delayed for IMS segment

  • OTHR
    Application delayed for an unidentifiable resource

  • Chart
    50 columns of numbers depicting the time that is spent by the program either executing on a CPU or delayed for data for each period.
    The percentages shown represent from 0% to 100% of the total resource demand. When the percentage is 5% or less, a '.' is displayed. When the percentage is between 5% and 95%, a single digit from 0 to 9 is displayed. When the percentage is 95% or greater, a '+' is displayed.

Monitor Messages

Messages that are issued by the CA MAT Server Space during the monitored period are displayed here. These messages provide additional information about CA MAT execution and completion.

Monitor Options from Profile

Monitor options that you specified in the Monitor Criteria panel are displayed here.