There might be some confusion about ZCOM error codes versus
ZCOM status codes because both are returned (via different call
mechanisms) by ZCOM API calls, and ZCOM status codes look like they
are reporting error conditions.
A ZCOM error code is intended to report status, typically problems, about an application's
ability to interact with the ZCOM subsystem. Since an application
uses the ZCOM API to interact with the ZCOM subsystem, ZCOM error
codes are returned from ZCOM API calls. An error code may indicate
a problem with the current state of the ZCOM subsystem, for example,
a down state, a problem with the parameters in the API call itself,
a problem with the current state of ZCOM tables allowing the application
using the ZCOM API calls to interact with the ZCOM subsystem, or
a problem with system resources, etc.
A ZCOM status code reports on the state of application-data
messaging, the state of the communication protocols in firmware
down on the ACC card, and the state of the physical line used to
send/receive application data from remote entities. ZCOM status codes are NOT always about problems. These
status codes are value-neutral. It is up to the application to determine
whether the particular status indicates a problem condition. For
example, if a communications link is reported as down, this may
be an acceptable situation for an application if it expects the
link to be down at that particular time. To summarize:
| | ZCOM Error Codes | ZCOM Status Codes |
|---|
| Purpose | Report on application's ability to
interact with ZCOM | Report on the condition of messaging and protocols |
| Conditions types reported | Problem conditions | Up to the application to interpret as a problem
or not a problem condition |