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.
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. |
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 |
|
- Topology Query Language
- Topology Query Language (TQL) Overview
- Creating TQL Queries in the RTSM Managers
- Viewing TQL Query Results
- Compound Relationship
- Join Relationship
- Query Node Conditions
- Complex Type Condition
- Subgraph Definition
- The Use Update Value Policy Qualifier
- How to Define a TQL Query
- How to Add Query Nodes and Relationships to a TQL Query
- How to Define a Compound Relationship – Scenario
- How to Define a Join Relationship – Scenario
- How to Define an Attribute Condition – Scenario
- How to Define a Complex Type Condition - Scenario
- How to Create a Subgraph Definition – Scenario
- Shortcut Menu Options
- Attribute Operator Definitions
- TQL Logs
- Topology Query Language User Interface
- Troubleshooting and Limitations
TQL Logs
This section contains definitions for TQL parameter log files.
The log name is cmdb.pattern.statistics.log.
Log File | Description |
---|---|
Purpose | General calculation data for each TQL query, updated at predefined intervals. |
Information Level |
The following information is given for each TQL query:
|
Error Level | Not available. |
Debug Level | Not available. |
Basic Troubleshooting |
|
The log name is cmdb.audit.short.log.
Log File | Description |
---|---|
Purpose |
You can use this log to follow the results of TQL queries. |
Information Level | Not available. |
Error Level | Not available. |
Debug Level |
|
Basic Troubleshooting |
|
The log name is cmdb.incremental.statistics.log.
Log File | Description |
---|---|
Purpose | Traces the calculation procedure, full or incremental, of every query. |
Information Level | Not available. |
Error Level | Not available. |
Debug Level |
|
Basic Troubleshooting |
Monitors the calculation process. If a specific query calculation takes a long time, check if it is a full or incremental calculation:
|
The log name is cmdb.incremental.splitter.log.
Log File | Description |
---|---|
Purpose | Monitors the incremental splitter result made during an incremental calculation. |
Information Level | Not available. |
Error Level | Not available. |
Debug Level | Gives the set of query node numbers of each query graph created by the incremental splitter. |
Basic Troubleshooting | If the TQL result calculated by the incremental calculator is wrong, verify that the splitter result is correct. |
The log name is cmdb.incremental.detailed.log.
Log File | Description |
---|---|
Purpose | Monitors the incremental calculation process. |
Information Level | Not available. |
Error Level | Not available. |
Debug Level |
Each incremental subcalculation entry includes the following:
|
Basic Troubleshooting | Follows the basic steps of an incremental calculation. |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: