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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Configuration Management System (CMS)2018.05

TQL Parameter Logs

This section contains definitions for TQL parameter log files.

Pattern Statistics Log

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: name average, minimum, and maximum calculation times number of calculations last calculation time result size
Error Level	Not available.
Debug Level	Not available.
Basic Troubleshooting	Verify that a specific TQL query was updated. Evaluate a TQL query's calculation time. Evaluate a TQL query's result size.

The log name is cmdb.audit.short.log.

Log File	Description
Purpose	CMDB state changes, CI Type changes, and TQL query results. You can use this log to follow the results of TQL queries.
Information Level	Not available.
Error Level	Not available.
Debug Level	Final calculation for TQL queries is logged. If the final TQL query calculation is unchanged from the previous calculation, this is noted. If the final TQL query calculation is changed from the previous calculation, results of the CIs and relationships are recorded in the detailed log. The number of CIs and relationships are recorded in the short log.
Basic Troubleshooting	Use this log to verify which notifications are published by the TQL query subsystem. Check the section at the end of each result. This section includes added, removed, and updated CIs and relationships. Track the CIT changes and see if the query results also change. You can thus correlate the CIT changes to the results of the query calculations.

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	Gives the date, time, query name, and whether an incremental statistic calculation was performed (yes/no). If an incremental statistic calculation was not performed, states the reason, the number of subcalculations (relevant for incremental calculations only), and the complete calculation time.
Basic Troubleshooting	Monitors the calculation process. If a specific query calculation takes a long time, check if it is a full or incremental calculation: If full, check whether a full calculation is necessary. If incremental, check how many subcalculations have been performed.

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: the trigger query node the number of elements classified to the trigger query node whether the subcalculation step is driven by new elements added to the model or by existing elements the calculated query graph
Basic Troubleshooting	Follows the basic steps of an incremental calculation.