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 |
|
System alerts
System alerts are system events that have passed a pre-defined threshold and that Service Manager writes to the server log (default: sm.log). System alerts contain information about the health and performance of the Service Manager installation. System administrators can define the conditions that trigger system alerts from the Service Manager initialization file.
The server log lists all the system events that have passed a pre-defined threshold. System administrators can review the server log to determine the health and performance of their Service Manager installation. By default, the server log is located in the <Service Manager>\Server\logs folder. System administrators can change what information Service Manager writes to the server log as well as the location of the log from the Service Manager initialization file.
System alert message format
Service Manager writes system alerts to the server log using the following format:
[Process ID] [Date and time] [Alert category]-[Alert type]-[Alert item], [Alert text]
| Alert format | Description |
|---|---|
| [Process ID] | This is the unique numerical identification of the process that generated the system event. |
| [Date and time] | This is the date and time that Service Manager recorded the system alert. |
| [Alert category] | This is one of the four basic alert categories. For more information about alert categories see the list of system alerts. |
| [Alert type] | This is a numerical value that describes the exact conditions that caused Service Manager to record the system alert. For more information about alert types see the list of system alerts. |
| [Alert item] | This is the application, resource, or user that generated the system event. |
| [Alert text] | This is a text description of the user and actions that generated the system event. |
Sample system alert messages
The following are sample system alert messages:
1712 11/03/2003 07:59:00 Performance-1-company, Full File Scan for
query involving fields {show.company} ; user(falcon),
application(display), panel(show.rio)
1712 11/03/2003 07:59:06 Performance-2-cm3t, Partial File Scan for query
involving fields {header,parent.change, header,open} ; user(falcon),
application(display), panel(show.rio)
Set a system alert parameter
Applies to User Roles:
System Administrator
To set a system alert parameter, follow these steps:
- Stop the Service Manager server.
-
Open the sm.ini file in a text editor.
This file is in your Service Manager RUN directory.
- Type the system alert parameters you want to add.
- Save your changes.
-
Restart Service Manager.
Service Manager uses your new system alert parameters.
List of system alerts
Service Manager uses the following alert categories.
- Limits
- Mapping
- Performance
- Stalled
Each alert category has a list of alert types that describe what system event conditions triggered the system alert.
Limits
| Alert type | Description |
|---|---|
| Limits-1 | The database pool is nearly full. The alert item lists the pool number. This alert type is obsolete in Service Manager. |
| Limits-2 | A user's virtual memory usage exceeds the alertvirtuallimit parameter. The alert item lists the name of the user. |
| Limits-3 | A user's CPU usage exceeds the alertcpulimit parameter. The alert item lists the name of the user. |
| Limits-4 | The system shared memory is critically close to full. |
Mapping
| Alert type | Description |
|---|---|
| Mapping-1 | A database field has been truncated and mapped in a compressed format. The alert item lists the truncated file and field names. |
| Mapping-2 | There is a duplicate mapping for a single SQL field. The alert item lists the file name with the duplicate mapping. The alert text lists the field names with the duplicate mapping. |
| Mapping-3 | A query could not be translated into SQL. The alert item lists the file name. The alert text lists the query and the function that could not be translated into SQL. |
| Mapping-4 | There is a field that cannot be used in an SQL query because of its data type. The alert item lists the file and field names. |
Performance
| Alert type | Description |
|---|---|
| Performance-1 | There has been a non-keyed query request that exceeds the alertquerylimit parameter. The alert item lists the name of the file that was the target of the query. You can avoid this alert by creating a key to satisfy the query. |
| Performance-2 | There has been a partially keyed query request. The alert item lists the name of the file that was the target of the query. You can avoid this alert by creating a key to satisfy the query or set a reasonable value of environment parameter alertquerylimit. |
| Performance-3 | The system has been waiting for a query to return a result but the query has exceeded the alertwaitlimit parameter. The alert item lists the name of the lock. |
| Performance-4 | The system has been waiting for a lock to release a resource but the lock has exceeded the alertholdlimit parameter. The alert item lists the name of the lock. |
| Performance-5 | There has been a query request that exceeds the alertquerylimit parameter. The alert item lists the name of the file that was the target of the query. You can avoid this alert by creating a key to satisfy the query. |
| Performance-6 | There has been a query request that exceeds the alerthitratio parameter. The alert item lists the name of the file that was the target of the query. You can avoid this alert by creating a key to satisfy the query. |
| Performance-7 | When building a global list, the system displays an information message if the global list contains more than 500 items. |
Stalled
| Alert type | Description |
|---|---|
| Stalled-1 | Obsolete alert. This functionality has been removed. |
| Stalled-3 | The IR irqueue is stalled. The number of records in the irqueue exceeds the alertirqueuelimit parameter. |
| Stalled-4 | Obsolete alert. This functionality has been removed. |
| Stalled-6 | The IR irqueue is stopped. The first record in the irqueue is not changing. |
System alert filters
System administrators can create system alert filters to hide alert messages about system events that they deem are not detrimental to the system. System administrators can define system alert filters from the Service Manager initialization file. To filter out a system event, system administrators can add the alertfilters parameter to the particular event in the initialization file.
Related topics
