Traces
Many components of the OMEGAMON® for Storage product contain dynamic tracing capability. For these components you can start and stop traces while the agent is running and those traces will display information specific to that one component in the RKLVLOG. Whenever possible, you should use these component-specific traces instead of the DEBUG(ON) switch mentioned in Chapter 1 under the section Tips regarding the collection of diagnostic data. The DEBUG(ON) switch will flood the RKLVLOG with information about all components in the product, making it difficult to find information pertinent to the problem you are reporting.
| Component | Trace Identifier |
|---|---|
| Application Monitoring | APLM |
| Command Intercept | CMIN |
| Dataset Attributes Database | DADB |
| Dataset Groups | DSNG |
| HSM Common Recall Queue | HCRQ |
| Storage Toolkit | SGTK |
| DASD Space Monitoring | SPAC |
| STK VTS Monitoring | STKT |
| User DASD Groups | UDGR |
Dynamic tracing can easily be started and stopped by issuing modify commands to the TEMS started task.
Here is the command format:
F stc_name,S3DB START,trace_identifier
F stc_name,S3DB STOP,trace_identifier