IBM Tivoli OMEGAMON XE for IMS on z/OS V410 IBM Tivoli OMEGAMON XE for IMS on z/OS V410 Response Time Analysis data missing from Tivoli Enterprise Portal workspace This presentation describes a problem with Version 410 of OMEGAMON® XE for IMS™ in which the two product-provided workspaces dealing with Response Time Analysis (RTA) data were blank. It also provides a quick workaround for the issue. RTA data missing from Tivoli Enterprise Portal workspace RTA data missing from Tivoli Enterprise Portal workspace Customers reported empty RTA workspaces in Version 410 Additional product customization was necessary to port Response Time Analysis data Resolved in Version 420 by expanding the capability of the workspaces involved RTA data missing from Tivoli Enterprise Portal workspace. After Version 410 of OMEGAMON XE for IMS on z/OS® was released in late 2007, it was discovered that the two new RTA workspaces had no data in some customer environments. Some research showed that the data necessary to populate these workspaces was only available if some default product settings were customized in the Global member. This customization is described in more detail in the User's Guide. Because work was already underway for Version 420, the new release was updated with sufficient logic to use the existing data. However, Version 410 still required customers to do a bit of work. Example of empty RTA workspace Example of empty RTA workspace Example of empty RTA workspace. As you can see in this example of an RTA workspace, data is missing from all views. How RTA data is collected How RTA data is collected OM/IMS Classic started task acts as the collector Agent started task automatically detects the existence of Classic started task and seeks input Classic Agent How RTA data is collected. As the XE interface to the product has matured, more data collection activity has been reproduced within the Agent started task. For customers who still prefer the 3270-based interface known as Classic or CUA, the Classic started task continues to function as the data collector. Currently, one of the very few collection functions that has not been copied to the Agent started task is for RTA data. That functionality still remains solely in the Classic task. Therefore, to collect RTA data and present it within Tivoli Enterprise Portal, the IMS system being monitored must have a Classic started task running with RTA data collection enabled. The Agent started task periodically scans the system for Classic data that might be available for a configured IMS system. It then adds that data to what has already been provided to the portal client. Customization of Global member required Customization of Global member required Default Global member in RKANSAMU(KOIGBLxx) only defines CLASS based groups Version 410 RTA workspace logic requires PSB or TRAN based groups Global member does not allow TRAN=* or PSB=* Solution: define multiple groups such as $OIGROUP ID,TRAN=A*,GROUPS=10 $OIGROUP ID,TRAN=B*,GROUPS=10 $OIGROUP ID,TRAN=C*,GROUPS=10 Customization of Global member required. OMEGAMON for IMS has always split up response time analysis data into user-defined groups. These groups can be defined in a number of ways, including IMS transaction name, PSB name, or IMS Class. By default, this Global member defines Group 1 as all IMS Class 1 transactions, Group 2 as IMS Class 2 transactions, and so on. All of the default groups are based on the IMS Class with which a transaction is defined. Version 410 of the XE interface requires RTA data that has been collected by a Transaction or PSB defined group. Therefore, some Global member customization is required. Instructions for this customization are included in the User's Guide, but be aware that you must add some Groups that are defined with either the TRAN or PSB keywords instead of the default CLASS based examples. Currently a completely generic group like TRAN=* or PSB=* is not recognized, but you can create groups such as TRAN=A* and TRAN=B* as an alternative. Create all 26 letters of the alphabet to cover all of the IMS transaction name prefixes possible. After updating the Global member, you must assemble and link it into your RKANMODU load library using JCL found in RKANSAMU. You must then recycle your Classic started task. Example of RTA workspace with correct Global Example of RTA workspace with correct Global Example of RTA workspace with correct Global. Shortly after the Global member is assembled and linked into place, your RTA workspaces should begin to reflect the newly available data. Notes Notes Classic started task collects RTA data only on IMS write to OLDS, so low-throughput systems might take a while to populate a workspace Technote 1396840 describes new RTA workspaces Technote 1389976 describes necessary updates to Global for V410 V420 workspaces updated to use even CLASS based groups as input Notes. Because OMEGAMON for IMS cannot see the IMS input data until the log data is written (called an OLDS write), you might have to wait a while until IMS writes that data. On low-use systems you can force such a write by using the IMS /CHE command to cause an IMS checkpoint to be written. To prevent any unexpected consequences, always confer with your IMS systems programmer before attempting to issue any IMS commands. Two Technotes provide additional information about this issue: Technote 1396840 describes the new RTA workspaces and Technote 1389976 describes how to update your Version 410 Global member appropriately. Note that the logic in the Version 420 workspaces has been updated to use even the default CLASS based groups to provide the RTA workspaces with the data they need. Feedback Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send e-mail feedback: mailto:iea@us.ibm.com?subject=Feedback_about_missing_rta_data.ppt This module is also available in PDF format at: ../missing_rta_data.pdf You can help improve the quality of IBM Education Assistant content by providing feedback. Trademarks