Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

DSNMCom: The I Process Test Utility
Distributed Systems Network Management (DSNM) Subsystem Interface Development
Guide—109759 7-13
DSNMCom Messages
Cause. DSNMCom was unable to open the specified file.
Effect. If the error occurred on the input or output file, DSNMCom abnormally ends
after writing a brief description of the error to the home terminal.
If the error occurred on the process file, the process file remains closed; any previously
opened process file remains open.
Recovery. See the Guardian Procedure Errors and Messages Manual for a description
of the specific file system or sequential I/O (SIO) error and the appropriate recovery
action.
Cause. DSNMCom was unable to open the specified STARTUP parameter value in the
$SYSTEM.SYSTEM.DSNM file (a section named env-name) during the DSNM
initialization process because the specified section name is too long. The maximum
acceptable length for env-name (ZDSN-MAX-PARAMNAME) is 32 bytes.
Effect. A fatal error is reported, and DNSM is not started.
Recovery. Correct and reissue the command. Refer to the Distributed Systems
Management Solutions (DSMS) System Management Guide for information on DSNM
process startup message parameters.
Cause. The command did not include an expected character.
Effect. DSNMCom is not started up.
Recovery. Correct and reissue the command.
Cause. During the initialization of DSNM, inappropriate configuration input was
submitted, or no configuration was submitted.
Effect. DSNM and DSNMCom cannot be started.
Recovery. Check your configuration files and try the DSNM initialization again. If the
problem persists, contact your Tandem representative. Be prepared to describe the
problem in detail as recommended in “What to Prepare Before Contacting Your Tandem
Support Representative” on page B-1.
OPEN ERROR nn ON filename
ERROR -- Section name too long
ERROR -- Expecting <space> <comma> or <semi-colon>
ERROR -- DSNMCom can't continue