Monitor History View

The Monitor History View lists all instances or runs of a particular monitor profile.

To view history in the Monitor History view

  1. Verify that a server connection is available and active in the Monitor Profiles view.

  2. Right-click a profile name in the Monitor Profiles view and select Open History.
    A table showing the history information is displayed. For more information about the fields such as measured job, run number, start date, CPU time, EXCP count, SIO rate, and the percentage of active, wait, and non-dispatch samples, see View Monitor History in the CA Mainframe Application Tuner product documentation.

    Note: Instances only show when invoked from the GUI or from using batch utility TNBATXML.

  3. Click the down arrow images/download/attachments/382363129/1856919.png on the Monitor History view toolbar to display the following actions:

    • Reset View
      Resets the current view. The Monitor History view reloads to display the most current measurements of monitors.

    • Filter Elements
      Allows data in a table to be filtered.

    • Show Columns
      Allows table columns to be customized.

    • Analyze
      Initiates analysis of the data that has been collected during a monitor session. All four analysis options (Analyze Normal, Analyze All, Analyze Active and Analyze Wait) are requested and downloaded from the mainframe to your workstation. When the download completes, the Analysis view opens and you can select the analysis option you want to use.

      Note: Alternatively, you can select the monitor name and click the Analyze toolbar icon images/download/attachments/382363129/1971018.png on the Monitor Profiles view.

    • Delete
      Deletes the history record.

Monitor History View Columns

The following columns are displayed in the History View:

  • EXCP Count
    Number of input/output operations for the job-step during the monitoring period. Including i/o counts not reflected at the DD name level.

  • SIO Rate
    Number of start I/O operations per second for the job during the monitored period

  • % Active
    Percentage of active samples. This number is ratio of samples with CPU active to the total number of samples.

  • % NonDispatch
    Ratio of samples when the job was ready to run but prevented from running because of higher priority work in the system to the total number of samples.

  • % Proc Delay
    Percentage of the monitored period when CA Mainframe Application Tuner detected the address space was unable to be dispatched because a processor could not be made available. While this is occurring, the application is unable to execute.

  • % Swapped
    This number is the ratio of samples when the job was swapped out to the total number of samples.

  • Observation Rate
    The final observation rate calculated by CA Mainframe Application Tuner.

  • Samples Collected
    This number can vary from the number shown during an Interactive Analysis, since an Interactive Analysis will adjust the sample count depending on the type of analysis performed.

  • Samples Used
    Total number of samples used for data analysis.

  • Elapsed Time
    Length of time the monitor session ran in HH:MM:SS

  • Measured JobID
    JES job identifier of the the job that was monitored. This field is valid for jobs that were initiated under a job entry subsystem.

  • Measured ASID
    Address space identifier of the job which was monitored.

  • Exists
    Displays data set availability

    • YES
      Data is available and has not been migrated

    • NO
      Data set is not found

    • ML?
      Data exists but is migrated to the DFSMShsm ML1 or ML2 migration pool.

      • ML1 migration generally goes to disk.

      • ML2 migration generally goes to tape.

    • INV
      Data set name is invalid. If INV is displayed, check the entry data set name.

    • PER
      A program error occurred other than the data set not being found. See your technical support staff for more information.

  • Requested Observations
    Number of observations to be collected.

  • Strg Abo
    Virtual storage above the 16MB line used by the job being monitored.

  • Strg Bel
    Virtual storage below the 16MB line used by the job being monitored.

  • Page in Count
    Number of page-in operation for the job during the monitored period. A high value may indicate job delays.