Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

Distributed Systems Network Management (DSNM) Subsystem Interface Development
Guide—109759 B-1
B
DSNM Error Codes
Scope of This Appendix
This appendix lists the ZDSN^ERR values that you may send back to the frame in the
Z^RESULT field of a formatted output object structure, or that may be returned to you
from a call to a DSNM library procedure.
Reporting Errors
Errors that do not terminate a command must be associated with an object (for instance,
an object name that is unknown to the subsystem) and are reported in the Z^RESULT
field of a formatted output object structure. In general, errors associated with a
particular object should not terminate the command, although there may be exceptions
for individual subsystems.
The Z^RESULT result code must be one of the ZDSN^ERR values defined in this
appendix. In addition, the output object structure must contain all entries appropriate for
the command being executed, including the fully qualified object name.
If the result code doesn’t fully describe the error, additional descriptive information
should be appended as result text (ZDSN^VTY^RESULTTEXT). The result text must
not duplicate the information of the result code itself: presentation services substitute
the text below for the result code in the user’s error display.
What to Prepare Before Contacting Your Tandem
Support Representative
Some of the problems you encounter might require assistance from a Tandem support
representative. Before you contact your representative, gather the following relevant
information:
•
How DSNM is installed.
•
Whether DSNM was started before starting NonStop NET/MASTER MS, or
NonStop NET/MASTER MS started DSNM.
•
The VPROC of any utility executed by PROGRUN or OPSYS (with NonStop
NET/MASTER MS environments).
•
History of the problem: has it happened before? If so, when and under what
conditions did it happen? Can you reproduce it? If so, state how to reproduce it.
•
List of any recent changes to the system, including, but not limited to, new or
changed configuration parameters, new or upgraded software modules, new
hardware components, or changed NCL procedures (with NonStop NET/MASTER
MS environments).
•
List of the output of any tracing associated with the problem, if appropriate to the
environment or nature of the problem.