Troubleshooting and Limitations – EView Agent Discovery

Troubleshooting Mainframe by EView discovery falls under two broad categories:

• Troubleshooting the UCMDB/DFM Mainframe discovery process:

  • Validating correct triggers for discovery jobs, checking invocation of discovery jobs, checking probe logs for troubleshooting information, and so on

  • Manually invoking commands against the z/OS LPAR using the
    EView/390z Discovery Client

  • Validating connectivity between the EView/390z Discovery Client and the EView/390z Agent

  • Checking that the commands can be issued successfully and valid responses are returned from the z/OS LPAR

• Troubleshooting the EView/390z Agent.

The discovery troubleshooting process almost always starts when a discovery process fails to correctly discover CIs and relationships. It is important then to determine whether the root-cause of the issue is with the UCMDB/DFM discovery process (jobs, triggers, adapters, scripts, and so on) or with EView/390z Discovery for z/OS. Some steps that can be helpful in this troubleshooting process are:

• Ensure that UCMDB/DFM processes/services are running as normal.

• Ensure that all the Mainframe discovery packages are correctly deployed and that the discovery jobs are properly configured.

• Ensure that the EView/390z Discovery Client (version 6.3 or later) and EView/390z Agent (version 6.3 or later) are installed. If earlier versions are installed, the discovery might fail.

• Ensure that the EView/390z Discovery Client is properly installed on the Data Flow Probe machine and its services are installed correctly and running.

• Ensure that the LPARs to be discovered are correctly configured in the EView/390z Discovery Client.

• Run the discovery job that is having issues and check the discovery logs for messages related to the invocation of jobs and execution of commands.

  • If there appears to be a problem with the invocation of discovery jobs, discovery script syntax errors, or CI reconciliation errors, troubleshoot them as you would any discovery process in UCMDB.

  • If the logs show that the discoveries are failing due to commands not being issued against the EView/390z Agent, identify the failing command from the probe debug log files, and manually try to invoke the relevant commands using the EView/390z Discovery Client. For more information, contact EView Technology Inc.'s customer support.

Problem: Duplicate MainframeDB2Databases may occur because the root container of MainframeDB2Database is changed from MainframeSubsystems to Db2DatasharingGroup.

Solution: Clean up MainframeDB2Database CIs from UCMDB and rerun the DB2 by EView job.