A link to a terminal emulator session fails

If a link to a terminal emulator session fails, there are several techniques to use in order to resolve the problems with context sensitive linking to 3270 interface workspaces. The initial step is to ensure that your environment is suitable for the links to function.

The following conditions must exist for the scripts to function:
  • IBM Tivoli Monitoring and the Tivoli Enterprise Portal must be at V6.2.1 or higher. If you are not running the correct version, then the Tivoli Enterprise Portal client is unable to prompt the user for the user ID and password or provide the necessary values to the script.
  • The OMEGAMON AI for CICS level for both the monitoring agent and the product support on the Tivoli Enterprise Portal must be at least V4.1.0 with Interim fix pack 4. If the agent is back level then the agent does not have the correct version of the Service Task Details query and the Tivoli Enterprise Portal is not able to query the agent for the connection values.
  • The OMEGAMON for CICS (3270) session must be reachable by the terminal emulator session over a non-encrypted connection. The terminal emulator does not support encrypted connections at this time.
  • The logon panel that is displayed when the terminal emulator first connects to the host must support the entry of the command to log in to the OMEGAMON 3270 session for the product-provided scripts to function properly. Modified scripts can be created to handle alternative initial terminal emulator panels.
If you satisfy all of the previous noted conditions and the scripts still fail, you must investigate further. See the "Managing workspaces" topic in the IBM Z OMEGAMON AI for CICS: User's Guide for more details on 3270 linking, queries, and scripts.

If you are not prompted for a user ID and password when a link is executed, then the Tivoli Enterprise Portal client is not the correct version or there should be an error message displayed that describes the problem. If you are prompted for a user ID and password, but the terminal emulator fails to connect to the host, then it is necessary to verify that the correct host name and port are being used; these are auto discovered by the Service Task Details query. If the host name and port have not been specified during configuration, but in certain network configurations, the values returned might not be correct. These values are displayed in the user ID and password dialog, and you can modify them there if they are not correct. If the terminal emulator session connects to the host, but fails to display the correct OMEGAMON 3270 workspace, then it might be necessary to check and potentially modify the script being driven by the terminal emulator session.