Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

-202 ZDSN^ERR^OBJECTTOOLONG or
ZDSN^ERR^OBJTOOLONG
B-8
109759—Distributed Systems Network Management (DSNM) Subsystem Interface
Development Guide
DSNM Error Codes
-202 ZDSN^ERR^OBJECTTOOLONG or
ZDSN^ERR^OBJTOOLONG
Cause. You typed an object name that is longer than the maximum allowable length.
Effect. Your command is not executed.
Recovery. Reissue the command with a shorter name.
-204 ZDSN^ERR^BADARGUMENT
Cause. There is an internal problem in the software that issued the message.
Effect. The effects of this problem vary, depending on the situation.
Recovery. Contact a Tandem representative. Prepare the necessary information as
suggested in “What to Prepare Before Contacting Your Tandem Support Representative”
on page B-1.
-206 ZDSN^ERR^NOTPUSHED
Cause. _POP^THREAD^PROCSTATE or _RESTORE^THREAD^AND^DISPATCH
was executed without a procedure having first been placed o n the stack.
Effect. Thread procedure not executed, and the command terminated abnormally.
Recovery. Check the source code to ensure that the thread procedure is saved before it
is dispatched again. If necessary, correct the source code.
-207 ZDSN^ERR^LIB^BADVALUE^OMITTED
Cause. One or more DSNM configuration parameter records contained an invalid
numeric value.
Effect. The library procedure reporting this error substitutes a value of -1 for the
erroneous value in the affected output parameter.
Recovery. You may be able to determine which value was unacceptable by looking for
a -1 returned in some field for which a positive value was expected. Using NETCOM,
check the DSNM configuration records in your DSNM configuration file, if any, and
correct the record.
Object Name too Long
Missing or Invalid Library Argument
Thread Proc was not pushed
Invalid DSNM configuration parameter values