ACC Error Guide

ZCOM Error Codes
Meanings of the Error Codes
Chapter 2 21
Meanings of the Error Codes
The error code returned by the ZCOM API library routine calls is zero if
the routine was successful, and non-zero if a failure occurred. The
ZCOM error codes, their symbolic names, their explanation, and (if
applicable) the corrective action are given below. Applications should
always use the symbolic name for an error as the error code value is
subject to change.
ZENBUSY (-1): ZNODE is too busy
Explanation: This error is returned when the high and low water
marks for the ZNODE queue have been configured to
the same value (TTGEN Flow-Control statement) and
the current number of messages on the ZNODE queue
has reached this value when the application program
requested a remote node operation. The ZCOM
subsystem will continue to reject remote requests until
the number of messages on the ZNODE queue drops
below high-water mark value.
Action: The system should recover from this condition if the
application has been properly coded. If the error occurs
consistently, check for possible problems with the
ZNODE daemon, host links, or adjust the Flow-Control
parameter in your TTGEN configuration file. Note that
this problem could occur normally if the application is
generating more data traffic then the network can
handle in given period of time.
ZESYSDOWN (-2): ZCOM subsystem is not started up
Explanation: System is not properly started, never started, or was up
and running and is now shutdown.
Action: Check the ZCOM message log file for any startup
errors. Correct any problems noted and rerun
ZMASTERD to restart the system (cold start).