Completing the configuration for OMEGAMON AI for CICS TGEdit online These are additional tasks to complete the configuration of OMEGAMON AI for CICS TG. Post installation configuration for transaction monitoring supportDepending on whether you are monitoring transactions through a Gateway daemon or through a WebSphere® Application Server with OMEGAMON AI for CICS TG, you must take specific steps to complete the configuration after installation. Monitoring CICS TG daemons bound to a TCPIP stack other than the one OMEGAMON AI for CICS TG Agent is bound toOn the same z/OS® LPAR, when the OMEGAMON AI for CICS TG Agent is not bound to the same TCPIP stack as is the monitored Gateway daemon, the agent must be provided with the IP address or hostname where the Gateway daemon is active, so that a successful remote connection can be established and statistical information can be collected.Defining a policy to periodically sweep away any orphaned transactions (optional)The transaction monitoring component of OMEGAMON AI for CICS TG keeps a table of all currently active transactions to calculate average response times and identify long-running transactions.Enabling warehouse agents on a z/OS hub monitoring server If you want to store long-term history data in the Tivoli Data Warehouse and your hub monitoring server is on a z/OS® system, and have not enabled the self-describing agent feature, then you must manually transfer the catalog and attribute files for the Warehouse Proxy agent and the Summarization and Pruning agent to the hub using Manage Tivoli Monitoring Services. Adding application support to a non self-describing agent enabled hub monitoring serverThis section describes how to add application support to a non self-describing agent enabled hub monitoring server on the z/OS® operating system. This section does not apply if you have the self-describing agent feature enabled.Parent topic: Completing the configuration