Verifying configuration if you configured only the Enhanced 3270 user interface

Use this verification procedure if did not configure Tivoli Enterprise Portal, but configured only the Enhanced 3270 user interface (enhanced 3270UI).

About this task

Start the components and verify their operation, as described in this section. If you encounter problems, see the IBM® Tivoli Monitoring: Troubleshooting Guide and the troubleshooting guides for each of your monitoring agents. If you see error messages, see IBM Tivoli Monitoring: Messages.

Procedure

  1. Start your hub Tivoli Enterprise Monitoring Server using the following command (shown using the default started task procedure name). Issue the following command from the z/OS® system console to start the Tivoli Enterprise Monitoring Server:
    S IBMDS
    Note: Use the stop command (P IBMDS) to stop the Tivoli® Enterprise Monitoring Server.
  2. Verify that the Tivoli Enterprise Monitoring Server has started successfully. You should see the following message displayed on the z/OS system console or in SYSLOG or in the RKLVLOG for the monitoring server (TEMS) started task procedure:
    KO4SRV032 Tivoli Enterprise Monitoring Server (TEMS) startup complete.
  3. From the z/OS system console, issue the following command (shown using the default started task procedure name) to start the IBM® Z OMEGAMON® AI for Networks monitoring agent.
    S IBMN3
    Note: Use the stop command (P IBMN3) to stop the IBM® Z OMEGAMON® AI for Networks monitoring agent.
  4. Verify that the IBM® Z OMEGAMON® AI for Networks Monitoring Agent has started successfully. You should see the following message displayed in the z/OS SYSLOG:
    IST1928I SNAMGMT CONNECTION TO KN3USER IS ACTIVE
    You should also see the following message displayed in the RKLVLOG for the IBM® Z OMEGAMON® AI for Networks monitoring agent:
    KN3PN001 IBM® Z OMEGAMON® AI for Networks INITIALIZATION COMPLETED
  5. From the z/OS system console, issue the following command (shown using the default started task procedure name) to start the enhanced 3270UI.
    S IBMTOM
    Note: Use the stop command (P IBMTOM) to stop the enhanced 3270UI.
  6. Verify that the enhanced 3270UI started successfully. You should see the following message displayed in the SYSPRINT log for the enhanced 3270UI:
    KOBGW0000I: Enhanced 3270 User Interface address space initialized successfully
  7. Verify that the enhanced 3270UI is configured correctly to collect the data that you want.
    1. Use this command to log on to the enhanced 3270UI from z/OS environment:
      LOGON APPLID(CTDOBAP)
      This command causes the enhanced 3270UI logon screen to be displayed.
    2. Log on to the enhanced 3270UI, using a valid user ID and password. If this log in fails, ensure that you completed the configuration required in Completing the configuration - IBM® Z OMEGAMON® AI for Networks, especially those tasks under Enabling security. The first screen you see is the Enterprise Summary workspace (KOBSTART), which serves as a “dashboard” for the IBM® Z Monitoring Suite that use the enhanced 3270UI. Each agent has a subpanel contained within this main panel.
    3. Enter this command to display the Enterprise Network Workspaces popup options menu:.
      NETMENU
      The Enterprise Networks Workspaces pop-up window is displayed.
    4. Type T on the command line and press Enter to display the Enterprise TCPIP Stack Performance Overview workspace. In this workspace, you should see IP data.

      Validate that the values for the System ID and TCPIP STC Name are correct, that is, that they match the system ID of the system on which you configured the IBM® Z OMEGAMON® AI for Networks monitoring agent and the TCPIP STC entries for the TCP/IP stacks that the IBM® Z OMEGAMON® AI for Networks monitoring agent is configured to monitor.

      If you see no data, view the agent RKLVLOG and verify that the agent has successfully connected to its the monitoring server. Search for this connection message:
      Successfully connected to CMS system_id:CMS using ip.pipe:#x.xx.xx.xx.xxx.
      Where system_id is the name of the system on which your monitoring server is running and x.xx.xx.xx.xxx is the IP address of this system.

      If these values are incorrect, ensure that you performed the system setup tasks described in Preparing your z/OS environment. See the RKLVLOG for more information.

    5. Type NETMENU on the command line and press Enter.
      The Enterprise Networks Workspaces pop-up window is displayed.
    6. Type M on the command line and press Enter to display the Enterprise Memory and CSM Storage Overview workspace.

      Validate that you see information about memory and CSM storage. Validate that the values for the System ID and TCPIP STC Name are correct, that is, that they match the system ID of the system on which you configured the IBM® Z OMEGAMON® AI for Networks monitoring agent and the TCPIP STC entries for the TCP/IP stacks that the IBM® Z OMEGAMON® AI for Networks monitoring agent is configured to monitor.

      If these values are incorrect, ensure that you performed the system setup tasks described in Preparing your z/OS environment. See the RKLVLOG for more information.
    7. Type NETMENU on the command line and press Enter.
      The Enterprise Networks Workspaces pop-up window is displayed.
    8. Type B on the command line and press Enter to display the Enterprise OSA Express Channels Overview workspace.

      Validate that you see correct information about the OSA Express channels in your environment. Validate that the System ID is correct, that is, that it matches the system ID of the system on which you configured the IBM® Z OMEGAMON® AI for Networks monitoring agent . Validate that the channel numbers displayed on this workspace reflect the correct OSA-Express devices connected to this system.

      If you see no data, verify that the z/OS TCP/IP SNMP Subagent (OSNMPD by default) and the OSA Express subagent (IOBSNMP or IOASNMP by default) are started on the TCP/IP stacks that are connected to OSA-Express devices. Ensure that you performed the OSA setup task described in Preparing your z/OS environment. See the RKLVLOG for additional information.

    Note: You can easily determine if the monitoring agent is online using the KOBMSNS Only Managed Systems workspace to determine if the IBM® Z OMEGAMON® AI for Networks monitoring agent is currently registered with the hub monitoring server. When the IBM® Z OMEGAMON® AI for Networks agent address space is active but shows the MS Online Status value as N (meaning it is offline), this usually means that a configuration error is preventing the monitoring services components from communicating with each other. It might also be that the IBM® Z OMEGAMON® AI for Networks agent address space had experienced an abend. More details about using this workspace and other troubleshooting scenarios are found in the IBM® Z OMEGAMON® AI for Networks: Troubleshooting Guide.

Results

For more information about the enhanced 3270UI, see the Using section of the IBM® Z OMEGAMON® AI for Networks documentation and the Reference section of the IBM Z Monitoring and Tivoli Management Services on z/OS: Shared documentation.