Managing IBM Tivoli Storage Manager › Defining a TSM Message Scanner Service

Defining a TSM Message Scanner Service

You can use the TSM Message Scanner service to scan the TSM servers for client and server-related messages:

• Scan Client Logs—CA SRM scans the Activity log for ANS-type client entries. The service can generate attentions to notify users about potential problems on TSM clients, and set severity indicators on the TSM client object.
• Scan Server Logs—CA SRM scans the TSM server database for ANR-type messages. The service can generate attentions to notify users about potential problems on the TSM server, and set severity indicators on the TSM server object.

The registration wizard automatically creates an extra DSN for each registered TSM server for use with these services.

After you define the period during which you want the scanning service to scan the logs, you can:

• Extract all of the lines within a defined period to a file specified in the TSM node configuration (the Extract file). You can also specify any lines not to be included in the Extract file.
• Scan all lines within a defined period and issue alerts when one or more of the following criteria are met:
  • Number of times a string appears in log lines
  • Number of times an error message appears in log lines
• Scan all the lines within a defined period and collect those containing defined substrings to a file specified in the TSM node configuration (the Results file).
• Assign severity levels to specified messages.

The conditions that control the operation of the scanning service are defined in the Pattern file.

The two services place their results in the TSM Activity Log table. This new table is purged based on the data retention parameter.

Note: When defining TSM services, ensure that there is adequate free space on the TSM servers to be scanned. The temporary tables created by the services require additional space.