19 special troubleshooting and recovery procedures, Running traces on dsm/scm components, Enabling traces – HP Integrity NonStop H-Series User Manual
Page 193
19 Special Troubleshooting and Recovery Procedures
This section provides troubleshooting and recovery procedures that should only be used under the
direction of HP support personnel.
Topics discussed in this section include:
•
“Running Traces on DSM/SCM Components” (page 193)
•
“Running Traces on the NonStop Software Essentials Client Component” (page 202)
•
“Running Traces on the NonStop Software Essentials Server Component” (page 204)
•
“Recovering Installed Products Using SIT2SCM” (page 204)
Running Traces on DSM/SCM Components
NOTE:
The trace function slows DSM/SCM processing and uses significant disk space. It should
be enabled only under the direction of HP support personnel.
You can start a trace for any DSM/SCM component on the host system or on any target system
that is network connected to the host. The Maintenance Interfaces provide trace functions to trace
the execution of their requests. Traces can help diagnose problems in DSM/SCM. These DSM/SCM
components can be traced from the specified DSM/SCM interfaces:
Interface
DSM/SCM Component
NonStop Software Essentials
Configuration Builder
(TACL)
Host Database Manager
NonStop Software Essentials, Target Interface
Input Supervisor
(TACL)
Object Manager
HP SIM Debug Trace
NonStop Software Essentials
NonStop Software Essentials, Target Interface
Target Activator
(TACL)
Target Object Manager
Target Interface
Target Schedule Manager
NonStop Software Essentials
Utility Server
When you enable tracing for:
•
The Schedule Manager or Object Manager, tracing begins immediately and lasts until you
disable trace or end the DSM/SCM session.
•
The Host Database Managers, tracing begins when any Host Database Manager receives a
request.
•
Any other DSM/SCM component, tracing begins when a request that uses the component
starts processing. If you disable trace while an enabled component is running, tracing for that
component is not disabled until the request finishes. If you do not disable trace, tracing continues
until you end the session.
Enabling Traces
•
“Enabling Component Tracing in NonStop Software Essentials” (page 194)
•
“Enabling Component Tracing (ZPHIHMI or ZPHITMI)” (page 194)
•
“Enabling Component Tracing (ZPHITI)” (page 194)
•
“Enabling Host Database Manager Tracing” (page 195)
•
“Enabling Object Manager Tracing” (page 195)
Running Traces on DSM/SCM Components
193