BackPak H4.00 Troubleshooting and Messages Manual

Troubleshooting
10 BackPak H4.00 Troubleshooting & Messages
In the distributed sample DSM.OPT, these commented options control the trace:
*TRACEFLAG INSTR_API GENERAL
*TRACEFLAG ALL,-NLS
*TRACEFILE d:\trace\dsmtrace1.txt
Remove the heading * to un-comment a line.
TRACEFLAG INSTR_API GENERAL will produces less traces than ALL,-NLS.
Logs in the workstation
The GUI produces occasional messages in the MS-Windows Event logging facility, in
a log named BackPakUiLog.
Manuals
When operating tape applications, the regular HP manuals are the main reference.
When troubleshooting tape-related problems these are especially useful to interpret
error messages about tape processing:
• Guardian Procedure Errors and Messages
• DSM/Tape Catalog Messages Manual
Some error numbers documented in this manual are included in EMS
messages produced by BackPak
• In DSM/Tape Catalog User’s Guide
see: CLASS TAPECATALOG DEFINE Consistency Checks
• In DSM/Tape Catalog Management Programming Manual
BackPak and other products such as ZSERVER issue some EMS messages
where a DSM/TC error is only described by an SPI error number. These SPI
error numbers are documented in this Programming manual.
• In HP NonStop TACL Reference
see: TAPE DEFINE Consistency Rules.
Sending case information to the Product Support
To document a case opened to the Product Support, provided tools help to collect the
various information.
A tool must be executed in each involved system at command prompt, producing
one or two files per system.
• The main NonStop system running the BackPak domain manager must always
be part of the collected systems.
• If the tape application was running on a peripheral NonStop system, this
peripheral system must also be collected.