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 |
|
Trace parameters that can be proactively activated
Activating a trace parameter in a production system causes additional load and causes log files to grow quickly, and therefore reduces the time interval covered by log rotation.
The following trace parameters can be activated in production environments even for a long time.
| Parameter | Description |
|---|---|
|
msglog:1 |
Writes all on-screen messages to the log file as well |
|
sqllimit:2 (or higher) |
Writes a message about the slow execution of any SQL statement (SELECT, INSERT, UPDATE, DELETE or others) |
|
debugdbquery:2 (or higher) |
Writes a message about slow SM queries taking longer than the specified number of seconds. The adding, updating, or deleting of records is NOT logged. Caution Do not set it to 999 because this is a special and verbose trace. |
|
rtm:2 |
Writes information about how long a user transaction took. This is basically the time from a user action until the next format is displayed. This parameter also causes information about native heap consumption to be printed to the log file so that sessions consuming a lot of memory can be identified. |
|
log4jdebug: com.hp.ov.sm.common.oom.LowMemoryHandler
|
The log4jdebug parameter is used to enable debugging messages for different java modules. The LowMemoryHandler module may be activated during production to monitor for a low memory situation of the servlets. |
| dbmonitorfiles:<dbdict1>[,<dbdict2>..] |
Logs a message whenever a record of the listed dbdicts is inserted, updated or deleted. The message contains the following information:
|
The following are examples of verbose trace parameters that must NOT be activated by default in a production system:
- rtm:3|4|5
- debugdbquery:999
- sqldebug:1|2
- debughttp
Activate these trace parameters only for special case analysis. It is recommended to contact Software Support if an issue cannot be analyzed otherwise. Refer to Running traces on the Service Manager server to identify the method to activate these parameters that creates the least additional system load and log file size.
Related topics
Dynamic debugging of user sessions or schedulers
