Troubleshooting installation and configuration problems
This information describes problems that might be associated with the installation and
configuration of OMEGAMON AI for CICS on z/OS base
product and the OMEGAMON AI for CICS
component.
Self-describing agent processing fails; Java root directory is not valid Symptoms of an unsuccessful self-describing agent installation Self-describing agent deletes all prior versions of the product installation record OMEGAMON AI for CICS product, the self-describing agent (SDA) tries to delete all the prior versions of the installation record, if any exist.A monitored system is displayed in the wrong place Tivoli Enterprise Monitoring Server , when the server and monitoring agents are brought back down and then brought up, the monitoring agents forward data to the wrong hub Tivoli Enterprise Monitoring Server .One or more CICS regions are not displayed on the interface; no communication between the agent and the region Tivoli Enterprise Portal navigation tree view or on the OMEGAMON enhanced 3270 user interface , issue a command to the agent for each missing CICS region.Verifying CICS region status with a situation in the Tivoli Enterprise Portal Tivoli Enterprise Portal . The CICSTG_Health_Critical situation is triggered persistently for a monitored CICS TG OMEGAMON AI for CICS TG component configuration, or the CICS TG configuration file (ctg.ini) does not have the Stats API port enabled.The CTGSTATS module failed for the OMEGAMON AI for CICS TG agent OMEGAMON AI for CICS TG monitoring agent a series of CEE dumplets and SYSOUT output might appear.Orphaned CICS TG transactions remain in active transaction workspaces OMEGAMON enhanced 3270 user interface and the Active Transaction Details workspace in Tivoli Enterprise Portal continue to report in-flight transactions that have completed and should be removed.Historical workspaces in Tivoli Enterprise Portal contain no data KFWITM220E Request failed during execution displayed in the Tivoli® Enterprise Portal message area.U200 Port in use message found in the RKLVLOG output, indicating an incorrect default port for TCP/IP profile U200 Port in use abend message in RKLVLOG, indicating a connection failure.