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 |
|
Research application errors
Processes call a number of RAD applications and execute a number of expressions, with a possibility of invoking more Processes afterwards. If any of the applications or expressions caused an error exit due to wrong syntax or wrong logic, this information can be found in the sm.log file.
Log sample:
Process panel run.pre.exp in RAD se.call.process encountered error in line 1 (se.call.process,run.pre.exp) Cannot evaluate expression (se.call.process,run.pre.exp) Cannot evaluate expression (se.call.process,run.pre.exp) Bad arg(2) oper = (se.call.process,run.pre.exp) Cannot evaluate expression (se.call.process,run.pre.exp) Cannot evaluate expression (se.call.process,run.pre.exp) Bad arg(2) oper = (se.call.process,run.pre.exp) Cannot evaluate expression (se.call.process,run.pre.exp) Bad arg(2) oper nullsub (se.call.process,run.pre.exp) Cannot evaluate expression (se.call.process,run.pre.exp) Bad arg(2) oper in (se.call.process,run.pre.exp) Cannot evaluate expression (se.call.process,run.pre.exp) Unrecoverable error in application: se.search.objects on panel call.list.engine Unrecoverable error in application: se.list.engine on panel call.process.1 Unrecoverable error in application: se.call.process on panel run.pre.exp
In this example (not out-of-box), the error occurred in se.call.process, run.pre.exp, or in other words, while evaluating the initial expressions of the Process. To find out which Process was causing the issue, go through the steps outlined above and note the process from the line:
DBACCESS - Cache Find against file Process found 1 record, query: process="upgrade.pcs"
Go to the Process record by the name of upgrade.pcs and check for any statements on the initial expressions tab. In this specific case, the expression will include the word nullsub. For example, the expression in question for this test may be
$L.icount=nullsub($L.icount, anynumberIwant)
The variable, anynumberIwant, is not a valid field, literal or variable, so it will have to be changed to prevent this issue.
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 docs.feedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: