Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
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.
