Client trace classes for the space management client
The space management client provides individual and aggregate trace classes. You can use aggregate trace classes for a shortcut to enable many related trace classes by specifying the aggregate trace class name.
The trace classes in table Table 1 are used for diagnosing problems with the space management client. To diagnose problems, use the trace class name with
the TRACEFLAG options in the dsm.opt file.
| Trace class | Description | Usage |
|---|---|---|
| PID | Displays the process ID on each trace statement. The PID is part of the SERVICE trace aggregate. | Use this trace class to diagnose problems that might involve multiple processes. |
| SERVICE | Displays general processing information for the client. The SERVICE aggregate includes all trace classes except MEMORY and *DETAIL classes. The SERVICE trace flag can generate a substantial amount of information. Consider using the tracemax option with the SERVICE trace flag. | Use this trace class when the nature of the problem is unknown. If the SERVICE trace flag is used, it is not necessary to specify other trace flags. For HSM daemon tracing, use this flag if the problem can be quickly re-created. |
| SM | Displays general processing information of the space management client. The SM class is part of the SERVICE or SMALL trace aggregate. | Use this trace class to diagnose problems that are related to HSM (hierarchical storage management). |
| SMALL | Displays information for HSM. | Use this trace class to enable all trace classes that are related to HSM. |
| SMXDSM | Displays DMAPI processing information. The SMXDSM class is part of the SERVICE or SMALL trace aggregate. | Use this trace class to diagnose problems that involve DMAPI processing information. |
| TID | Displays the thread ID on each trace statement. The TID class is part of the SERVICE trace aggregate. | Use this trace class to diagnose problems that might involve multiple threads of a single process. |