Verify the configuration

After completing the post configuration tasks described in this section, you are ready to confirm that the products and components can run and communicate with each other.

1. If you have not already done so, run the configuration verification job KCIJPVAL in each runtime environment to confirm that all the required data sets, members, and configuration jobs were created, and that the jobs completed successfully. If the configuration verification report shows that a required item is missing or that a job failed, repeat the necessary configuration steps.
2. After you have verified all runtime environments, validate the operation of all components and the communication between them as follows:

   Table 1. Validation of the runtime environment

   Configuration method

   Steps

   If you used the Configuration Manager or the PARMGEN configuration method, a job containing all the tasks configured within the runtime environment is available to use. Complete the adjacent steps.

   If your hub is on a distributed system or another runtime environment, start it. For more information, see the IBM Tivoli Monitoring: Installation and Setup Guide. Run the composite job to start all tasks within this runtime environment: /s xxxxSTRT where xxxx= %RTE_STC_PREFIX% (The PARMGEN default is IBM®.) Note: An equivalent xxxxSTOP job is generated for stopping all tasks within the runtime environment. In the RKLVLOG for each monitoring agent address space, look for the messages that indicate successful startup. Also look for messages indicating that the monitoring agents or remote monitoring server have successfully connected to the hub, if applicable. Consult the product-specific Planning and Configuration guides for more information. If you have enabled the self-describing agent feature, check the status of the self-describing agent application support at the hub monitoring server log, monitoring agent logs and finally any remote agent logs to ensure that the self-describing agent process has completed. For more information, see the IBM Tivoli Monitoring: Installation and Setup Guide.

3. Ensure that data collected by the monitoring agents is available on the user interface that you have chosen to use as follows:

   Table 2. Data validation on user interfaces

   User interface	Steps
   OMEGAMON® enhanced 3270 user interface	If you have not already done so, start the OMEGAMON enhanced 3270 user interface address space: /S IBMTOM Check the SYSPRINT of the OMEGAMON enhanced 3270 user interface and look for the messages that indicate a successful startup. The following message accompanied by no error messages indicates the completion of the OMEGAMON enhanced 3270 user interface startup process: KOBCM0058I: Registry Refresh statistics: Log on to the OMEGAMON enhanced 3270 user interface and check that the initial workspace panels contain data sourced from the monitoring agents within this runtime environment.
   Tivoli Enterprise Portal	On a distributed system, start the Tivoli Enterprise Portal Server and client. Log on to the Tivoli Enterprise Portal client. When the Tivoli Enterprise Portal starts, check for the managed system name that you have configured (listed under the z/OS® Systems entry in the Physical Navigator tree).

   Note: If you encounter problems, see the IBM Tivoli Monitoring: Troubleshooting Guide and the troubleshooting guide for each of your monitoring agents.