Response Time Analysis (RTA) workspaces

To help you to efficiently access the RTA workspaces, review this list of entries for the IMS subnode on the Tivoli Enterprise Portal Navigator.

The RTA component analyzes the response time of IMS transactions. You can use the RTA workspaces to view response times and performance-related information, resource availability, and data throughput.

The child topics list all the RTA workspaces and include descriptions of each RTA workspace, which helps you gather exactly the information that you require to detect and prevent problems. Based on the information that these workspaces provide, set up situations, change the situations, and verify that your changes improve performance.
Important: The child topics relate only to your Tivoli Enterprise Portal configuration. For information about using the OMEGAMON® enhanced 3270 user interface, see the OMEGAMON Enhanced 3270 User Interface Guide.

RTA Interval workspaces provide information about three user-defined intervals. The second interval must be a multiple of the first. The third interval must be a multiple of the second. For example, you can define intervals of 10 minutes, 30 minutes, and 60 minutes. When an interval expires, the contents are rolled (added) to the next interval and then cleared. Collection continues with empty buckets. In the previous example, the first set of buckets is cleared every 10 minutes, the second set of buckets is cleared every 30 minutes and the third set of buckets is cleared every 60 minutes.

Slots represent user-defined intervals (up to 48). The 24 hours that comprise a day are divided into slots; slots might not overlap, but can have gaps. RTA collects response time information into the current slot. Before you switch to a new slot, the system clears the new slot. Thus, response time information is collected for almost all of the prior 24 hours.

The RTA component breaks down the response time into the following components:
  • Input queue time (I)
  • Program input queue time (PI)
  • Processing time (P)
  • Output queue time (O)
  • Internal systems application response time (R0)
  • Total IMS internal response time (R1)
  • Local output time (LO)
Response time groups can consist of:
  • Transactions (class, transaction name, or PSB)
  • Logical terminal names (LTERM)
  • VTAM® nodes
Response time is displayed in several ways:
  • RTA Interval workspaces (IRSP)
  • RTA Slot workspaces (SRSP)
  • RTA Short Term History workspaces (GRSP)
  • RTA Response Time Exceptions workspaces (ARSP)
  • Worst Performing Transactions and Terminals workspace (RMON)
The following list of predefined workspaces mimics the structure of the Navigator tree, listed alphabetically in the IMS subnode:
  • IMS RMON Highest Response Times
    • IMS RTA Worst LTERMs
    • IMS RTA Worst Transactions
  • IMS RTA First 50 Exceptions
  • IMS RTA Group Summary
  • IMS RTA Interval Summary (or IMS All RTA Interval Summary for IMSplex)
    • IMS RTA Worst Group Detail
    • IMS RTA Worst Group Item Summary
      • IMS RTA Interval Item Detail
    • IMS RTA Interval Group Summary
      • IMS RTA Interval Group Detail
      • IMS RTA Interval Item Summary
        • IMS RTA Interval Item Detail
  • IMS RTA Item Summary
  • IMS RTA Minutes Group Summary
    • IMS RTA All Response Time Components for Group
      • IMS RTA Minutes Items for Group
    • IMS RTA All Response Time Components for Item
  • IMS RTA Slot Summary (or IMS All RTA Slot Summary for IMSplex)
    • IMS RTA Worst Slot Group Detail
    • IMS RTA Worst Slot Group Summary
      • IMS RTA Slot Detail
    • IMS RTA Slot Group Summary
      • IMS RTA Slot Group Detail
      • IMS RTA Slot Item Summary
        • IMS RTA Slot Item Detail
    • IMS RTA Slot Summary for Input IMS