 |
» |
|
|
|
|  | |
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).
ZENOZLU (-3): ZLU table
is full - Explanation:
All of the defined program ZLUs have been assigned
to ZCOM user programs. This could be caused by user programs that
allocate an excessive number of ZLUs without closing them after
use. This could also be caused by specifying a TTGEN Program-ZLU parameter value that
is too small. - Action:
If the problem was caused by mismanagement of the ZLUs
by the application program, then correct the application source
code. Otherwise, increase the number of ZLUs specified by the Program-ZLU parameter in the TTGEN
configuration file and regenerate the ZCOM subsystem (using ttgen
and zmon).
ZEZTERM (-4): ZLU must
be terminal type - Explanation:
A non-terminal ZLU is specified in a ZCOM call which expects
a terminal ZLU (for example, zcntl). - Action:
Correct the application source code.
ZEZPROG (-5): ZLU must
be program type - Explanation:
A non-program ZLU is specified in a ZCOM call which expects
a program ZLU (for example, zread). - Action:
Correct the application source code.
ZENODE (-6): Unknown
node number - Explanation:
The node number specified in the call is not defined
in the TTGEN configuration file. This could be due to a defect in
the application source code or an error in the TTGEN configuration
file. - Action:
Add or correct the Node-Definition parameters
in the TTGEN configuration file as needed. Otherwise, correct the
application source code.
ZEZLU (-7): ZLU is
out of range - Explanation:
An invalid ZLU was specified. The ZLU number must be
in the range from 1 to the total number of ZLUs (Terminal-ZLU and Program-ZLU parameters) defined in
the TTGEN configuration file. - Action:
Correct the application source code or increase
the Terminal-ZLU and/or Program-ZLU parameters in your TTGEN
configuration as needed.
ZEZCS (-8): ZLU checksum
does not match - Explanation:
The checksum for the specified ZLU does not match
the one stored in the ZCOM subsystem. This usually indicates that
the ZCOM subsystem has been shutdown and then restarted (causing
the checksum to be recalculated) without the program's
knowledge. This could also be caused by the application using the incorrect
checksum value for the supplied ZLU. - Action:
Correct the application source code or restart the application
as appropriate.
ZEMODE (-9): Illegal
request/control mode - Explanation:
The ZCOM routine was called using an illegal mode
or request code parameter. For example, calling zsend() with a mode value greater
than 8 or less than 0. - Action:
Correct the application source code.
ZEIFTNO (-10): Bad
interface number specified - Explanation:
An invalid Mux interface number was specified. This number
must range from 0 to the maximum Mux interface number defined in
your TTGEN configuration file. - Action:
Correct the application source code or your TTGEN configuration
file.
ZENAME (-11): Name
of ZLU not unique - Explanation:
The 7-character ZLU name specified is already used
by another program ZLU. The ZCOM subsystem requires a unique symbolic
name for each program ZLU. The zname() routine
can be used to determine if a symbolic name has been assigned to
another program ZLU. - Action:
Correct the application source code.
ZEFLUSH (-12): Message
has been flushed - Explanation:
This error is used as a response to a message sender.
It indicates the previously sent message was not properly read or
processed because the destination ZLU was closed (via zclos) or cleared (via zconfig). - Action:
No recovery action is needed. Check the destination program
for its ZLU being closed.
ZEREQUEST (-13): Error
in passing request data - Explanation:
Internal error indicating a problem in the ZCOM library
routines. - Action:
Contact your HP support representative.
ZEINUSE (-14): ZLU
already in use - Explanation:
The ZLU specified in the request to create a new
ZLU table is already used. That is, when programmatically creating
a physical or logical terminal table entry, use must either specify
an unused (spare) ZLU or allow the ZCOM subsystem to assign the
ZLU dynamically. - Action:
Correct the application program or use a ZLU value
of zero. A ZLU value of zero will cause the ZCOM subsystem to automatically
choose an unused ZLU.
ZENOLTT (-15): No spare
logical terminal tables - Explanation:
All of the logical terminal tables are assigned
and in use, leaving no spare ones to create a new terminal with.
This could be caused by applications dynamically creating new terminals
and then not deleting them when done. Alternately, you may have
configured the ZCOM subsystem with too few logical terminal table entries
for your needs. - Action:
Correct the application source code or increase
the size of the Logical-Term parameter
in your TTGEN configuration file.
ZENOPTT (-16): No spare
physical terminal tables - Explanation:
All of the physical terminal tables are assigned
and in use, leaving no spare ones to create a new terminal with.
This could be caused by applications dynamically creating new terminals
and then not deleting them when done. Alternately, you may have
configured the ZCOM subsystem with too few physical terminal table entries
for your needs. - Action:
Correct the application source code or increase
the size of the Physical-Term parameter
in your TTGEN configuration file.
ZEDOZINIT (-17): Must
call ZINIT first - Explanation:
The application called a ZCOM routine without first calling zinit(). The ZCOM routine zinit must be called before making
a call to any other ZCOM routines. - Action:
Correct the application source code.
ZERCVRFULL
(-18): Too many shared receivers - Explanation:
When an application requests adding a program ZLU as a
shared receiver, and the internal limit of the number of programs
that can be in the shared receiver list is reached, this error is
returned. - Action:
This is an application problem. The ZCOM subsystem allows
up to 64 program ZLUs in the shared receiver list for each terminal
ZLU. Most likely, an application is adding itself to a shared
receiver list and then failing to remove itself from the list before
it terminates. Investigate why there are too many shared receivers being
set. The shared receivers can only be cleared by using the appropriate
APIs, or by shutting down and restarting the ZCOM system.
ZEPORT (-19): Bad port
number specified - Explanation:
The Mux card port number supplied in the ZCOM routine
was invalid. The port number must be in the range 0 to 7, inclusive for
the Z7200A, Z7340A, and Z7400A cards. The port number must be in
the range 0 to 4 for the Z7300A card and in the range 0 to 1 for
the Z7350A card. - Action:
Correct the application source code.
ZEROUTE (-20): Remote
call sent to wrong node - Explanation:
This error is returned when the internal ZCOM consistency
checks detect a remote request that appears to have been routed
to the incorrect destination node. This could occur if the Node-Definition sections on the different
systems running the ZCOM subsystem are inconsistent. - Action:
Check the TTGEN configurations on all systems running
the ZCOM software and verify that the Node-Definition sections
have been correctly and consistently (e.g. IP addresses, host names, Remote-Node definitions, etc.) defined
amongst the different nodes. If the definitions are correct and
the problem still persist, contact your HP support representative.
ZECTYPE (-22): Bad
config. type in ZPORT call - Explanation:
The ZCOM zport routine
was called with an illegal configuration type. The configuration
type must be in the range 0 to 4, inclusive. - Action:
Correct the application source code.
ZENTOUT (-23): Remote
node timed out - Explanation:
This error is returned when a request issued to
a remote node has taken longer than the configured timeout value.
There are many reasons for this error. The remote node or link to
the node could have failed after the request was sent, the timeout
value may be too short for the amount of system activity at the remote
node, or the znode daemon may
have been deactivated. - Action:
Verify that the network communications are working properly
and that the remote node is up and functioning. Make sure that both
the remote and local ZNODE daemons are executing. Try increasing
the default timeout value specified in the Remote-Node definition
or change it programmatically using the zrntimer routine.
ZENODATA (-24): Input
queue is empty - Explanation:
The data retrieval routine failed because there
is no data in the input queue. This indicates an exception condition
rather than an error. It should be handled properly by the calling
program. - Action:
None.
ZEBLEN (-25): Illegal
buffer length - Explanation:
The buffer length specified is out of range (for
example, is negative). - Action:
Correct the application source code.
ZEZBAD (-26): ZLU not
initialized - Explanation:
The specified ZLU is not an allocated ZLU or it
has been closed (by zclos). - Action:
Correct the application source code.
ZENOTERM (-27): No
more terminals for this port - Explanation:
There is a maximum limit of 255 terminals that can
be assigned to any given port on a Z7200A, Z7350A, or Z7400A MUX
card. In addition, there may be a lower limit enforced based on
the type of protocol used on the port. That is, the limit is protocol
dependent. If an application attempts to programmatically add a terminal
to a port and this limit is exceeded, then this error is returned. - Action:
Correct the application source code.
ZEBUSY (-28): ZLU is
read by another program - Explanation:
The calling program is trying to read from a ZLU
that is being read by another program (that is, another program
is suspended and waiting for data from that ZLU). Usually, only
one program may be suspended waiting for data on a ZLU, unless all
programs reading that ZLU use "shared_read", having
set the ZCOM_ZREAD_SHARE (or ZCOM_ZPEEK_SHARE) bit in the mode parameter. Refer to the description
for zread(3x) or zpeek(3x) for details. - Action:
Correct the application source code.
ZENOPZ (-29): Must
have a primary ZLU - Explanation:
The request requires the calling program to have allocated
a primary program ZLU (using the zopen() routine).
For example, when using zsend with
the response mode, the response would be sent back to the caller's
primary ZLU by default. - Action:
Open a primary ZLU (using zopen)
before this call. Once opened, the same primary ZLU will be used
in all subsequent calls when required (so only one primary ZLU is
required). The user program is responsible for reading the primary
ZLU for any pending messages or responses. It is recommended that
a user program open its primary ZLU as early as possible to avoid
this error in other calls.
ZEVALUE (-30): Value
out of range. - Explanation:
The value specified is not in the correct range
for the request being issued. - Action:
Correct the application source code.
ZEWAIT (-31): Error
while awaiting response - Explanation:
This error indicates an internal defect in the ZCOM drivers. - Action:
Contact your HP support representative.
ZEIRRFULL (-32): Too
many interface requests - Explanation:
Some types of interface requests (.e.g restarting
an interface card) involve a series of complicated procedures that
are processed by the ZCOM server daemon, ZMON. Although ZCOM is
designed to process multiple requests in parallel, it can under
certain abnormal conditions overflow its internal interface request
queue. This error is returned when the internal interface request
queue is full. - Action:
Verify that the ZMON daemon is executing. Retry
the request again and if there are continuing problems, contact
your HP support representative.
ZEMLOOP (-33): ZLU
mapping goes into a loop - Explanation:
The zmapr call
allows a ZLU to be mapped to another ZLU. If the mapping is not
set up properly, the ZLU mapping chain may form a loop which would
result in all of the ZLUs in the chain being unusable. The zmapr routine rejects a request that
would create this condition. - Action:
Correct the application source code.
ZECONFIG (-34): Bad
config type or action - Explanation:
The config or action parameter specified in the zconfig() routine is invalid. - Action:
Correct the application source code.
ZEPTLINK (-35): Corrupted
PTT group linkage - Explanation:
This error is returned whenever the ZCOM subsystem discovers
an inconsistency in the group linkage of physical terminals. This
error could occur if the ZCOM kernel memory tables are corrupt. - Action:
Contact your HP support representative.
ZERCODE (-36): Illegal
request code in header - Explanation:
This error is returned when an internal defect in
the product is detected. - Action:
Contact your HP support representative.
ZETXCSYNC (-37): Tx
comp. with none outstanding - Explanation:
This error is returned whenever the ZCOM drivers detect
a software synchronization problem between the ZCOM drivers and
the Mux interface card firmware. - Action:
Contact your HP support representative.
ZETXCLEN (-38): Write
comp. lengths mismatch - Explanation:
This error is returned whenever the ZCOM drivers detect
a software synchronization problem between the ZCOM drivers and
the Mux interface card firmware. - Action:
Contact your HP support representative.
ZENOTXBUF (-39): Interface
out of Tx buffers - Explanation:
This warning is only reported by the ZCOM driver when
the Mux interface runs out of buffers to process new requests for
a particular port. This may occur when the Mux is in an abnormal
busy condition. Normally, this requires no operator intervention
and the Mux should recover. However, if it occurs consistently,
it may indicate a Mux firmware problem, a Mux overload, or an invalid
Port-Limit parameter. - Action:
Decrease Port-Limit parameter value in the TTGEN configuration
file; check the Mux firmware for Mux overloading using the zmntr "mx" command.
ZEBADBH (-40): Corrupted
buffer header - Explanation:
Data corruption within the ZCOM subsystem. - Action:
Contact your HP support representative.
ZEDSCLOCK (-41): DSC
function is disabled - Explanation:
This error is returned when a Dynamic System Configuration
function has been requested and the DSC functionality has been disabled
(see zconfig). Usually an application
program is suspended until DSC is enabled again. However, in certain
situation (e.g. a remote DSC request), the caller is not suspended and
this error is returned. - Action:
Try again later or use zconfig to
enable the DSC functions.
ZESPLOST (-42): No
buffer for remote response - Explanation:
This error is returned when a remote API request
is issued and there are no buffers available in the local system
to store the completion response returned by the remote system. - Action:
Check for abnormal buffer usage in the local ZCOM subsystem
or increase the size of the Buffer-Pool parameter
in your TTGEN configuration file on the local system.
ZEACTIVE (-43): Terminal
or interface is busy - Explanation:
A request (e.g. delete terminal) has been made that requires
the specified terminal or interface be in an inactive and disabled
state. However, it was determined that the terminal or interface
was not disabled, was still being accessed, or was processing an I/O
request. Usually, this error is returned because the application
tried to delete an interface or terminal without issuing all of the requests needed to place
the terminal or interface into a state where it can be deleted. - Action:
Correct the application program. Make sure there
are no other applications accessing the terminal or interface being
deleted.
ZEREOPEN (-44): Re-open
ZLU as different type - Explanation:
The routine zopen attempted
to re-open an existing ZLU that was not a program ZLU. Only program
ZLUs are allowed to be re-opened. - Action:
Correct the application source code.
ZEIRRFAIL (-45): ZMON
failed (see message log) - Explanation:
Some types of interface requests (e.g. restarting
an interface card) involve a series of complicated procedures that
are processed by the ZCOM server daemon, ZMON. This error is returned
when ZMON detects an abnormal condition that prevents it from completing
the requested function. - Action:
Check the ZCOM error log for ZMON error messages.
ZEHASDATA (-46): Must
clear terminal first - Explanation:
The requested function (e.g. terminal delete) requires all
data buffers linked to the terminal be removed (returned to the
ZCOM subsystem) before the terminal can be deleted. This error is
returned when the system finds that there are buffers still linked
to the terminal. There may be transmit buffers in the physical terminal table
or user data kept in the logical terminal data queues. Most likely,
the application failed to issue the correct ZCOM calls to remove
this buffer prior to attempting to delete the terminal entry. - Action:
Correct the application source code. The terminal should
be cleared using the ZCOM zconfig() routine.
ZEHASRVR (-47): Terminal
receiver not deleted - Explanation:
The requested function (e.g. terminal delete) requires that
all receivers for the terminal be deleted first. This error is returned
when the ZCOM subsystem finds that there are still receivers set
up for the terminal. - Action:
Correct the application source code. The receivers
for a terminal can be removed using the ZCOM zconfig() routine
(clear terminal function) or using the zset_rcvr() and
if needed, the zevent_rcvr() routine.
ZENOTDSB (-48): Must
be disabled first - Explanation:
The requested function requires the terminal to
be disabled. However, the terminal was found not to be in the disabled
state. - Action:
Correct the application program. Issue the appropriate ZCOM
calls to disable the object before making this request.
ZESUBCH (-49): Illegal
subchannel number - Explanation:
The application used an illegal subchannel number. Subchannel
numbers must be in the range 0 to 31 for ACC E1/T1 cards and must
be zero (0) for all other card types. - Action:
Correct the application program.
ZEHWUSED (-50): Hardware
already in use - Explanation:
The specified hardware bus and slot number is already assigned
to another interface card. - Action:
Correct the application program.
ZELIMIT (-51): Dest.
queue limit reached - Explanation:
The data send request has failed because this would cause
the destination ZLU to exceed its transmit queue limit. This can
result if the default queue limit has been set too small in the
TTGEN configuration file (Transmit-Limit parameter),
the application is sending data faster than it can be transmitted
to the device, or a defect in the design of the application program. - Action:
Correct the application source code or increase
the destination queue limit.
ZERNODE (-52): Receiver
ZLU must be local - Explanation:
In the current implementation, the zset_rcvr routine only accepts a
receiver ZLU on the local node. Any non-zero node number which is
not a local node number will be rejected with this error. - Action:
Use zero or a local node number with the receiver
ZLU.
ZEUPDATE (-53): Bad
update length or offset - Explanation:
In table update calls, such as zltup,
the offset and/or length supplied would have resulted in the update occurring
outside the boundary of the table. That is, the update would have
gone past the end of the particular table. - Action:
Correct the application source code.
ZERTYPE (-54): No such
receiver for this ZLU - Explanation:
The inbound or outbound receiver only exists in multiplexed
terminal ZLU. This error indicates the caller is trying to set such a receiver
for a non-multiplexed terminal. Refer to the description of zset_rcvr(3x) for acceptable settings. - Action:
Correct the application source code.
ZEORPROG (-55): OMX
receiver not program type - Explanation:
Data is being sent to an outbound multiplexed terminal,
but the outbound receiver ZLU is no longer a valid program ZLU (for
example, it is closed by zclos). - Action:
Check for a possible problem with the terminal ZLU
or the outbound receiver program.
ZENOOR (-56): OMX receiver
ZLU not defined - Explanation:
Data is being sent to an outbound multiplexed terminal,
but the outbound receiver ZLU is not defined. - Action:
Check for a possible problem with the outbound receiver
program.
ZEIFTINUSE (-57): Interface
table already in use - Explanation:
The specified interface table (interface card number)
is already defined and in use. An unused spare interface table entry
must be specified for this request. - Action:
Correct the application program or if needed increase the
number of spare interface tables by increasing the value of the Interface-Table parameter in your
TTGEN configuration file.
ZEORZCS (-58): Bad
OMX receiver ZLU checksum - Explanation:
Data is being sent to an outbound multiplexed terminal,
but the ZLU checksum is invalid. - Action:
Check for possible problems with the outbound receiver program,
or data corruption in ZCOM tables.
ZELQNO (-59): Bad logical
data queue number - Explanation:
The specified terminal logical data queue number
is illegal. Usually, logical queue is assigned through the zltqueue routine. Refer to the man
page zltqueue(3x) for details. - Action:
Correct the application source code.
ZEXNODE (-60): Different
nodes not allowed - Explanation:
Some of the ZCOM routines require two ZCOM addresses
in their parameter list. This error is returned when the two addresses
specified use different node numbers for a ZCOM routine that requires
the same node number for both addresses (e.g. a zqmve() call only allows moving data
between ZLUs on the same node). - Action:
Correct the application source code.
ZENDOWN (-61): Remote
node is DOWN - Explanation:
This error is returned whenever a request is issued
for a remote node that is not currently accessible by the local
ZCOM subsystem. That is, the local node has been unable to establish
communications with the specified remote node. There are many reasons
why this condition can occur. The ZCOM subsystem may not be running
on the remote system, the local or remote znode daemon
may have been shutdown, the network link(s) between the two systems
may be down, or the remote system may have failed. - Action:
Check for abnormal conditions in the network, ZCOM subsystems,
or hardware and correct as necessary.
ZELSIZE (-62): Inconsistent
storage size - Explanation:
Logical data storage is assigned to unique labels.
When a call is made to allocate logical data storage for an existing
label, but the requested size is different from that of the existing
label, the system rejects the call with this error. - Action:
Determine the allocation size for that label (using zscan) and correct the application
source code.
ZEBADSIZE (-63): Can't
get storage of this size - Explanation:
The zltstore routine
returns this error when the system cannot allocate logical data
storage for the requested size or the specified size is not a multiple
of 8 which is a storage size requirement. - Action:
Increase the logical data area size specified by
the Logical-Size keyword in
the TTGEN configuration file.
ZENOSLAB (-64): No
spare data storage label - Explanation:
This error is returned when all data storage labels
are used. Hence no new zltstore call
will be accepted. The maximum number of data storage labels is fixed
in the ZCOM subsystem and is not adjustable. - Action:
Re-design or reorganize the application to use less storage
labels.
ZENOLQ (-65): No spare
logical data queue - Explanation:
The zltstore routine
returns this error when the ZCOM subsystem cannot allocate a logical
data queue for the request because all queues have been allocated.
The number of logical data queues is fixed in the ZCOM subsystem
and is not adjustable. - Action:
Re-design or reorganize the application to use less
data queues.
ZENOQLAB (-66): No
spare data queue label - Explanation:
This error is returned when all data queue labels
are used. Hence no new zltstore call
will be accepted. The maximum number of data storage labels is fixed
in the ZCOM subsystem and is not adjustable. - Action:
Re-design or reorganize the application to use less
data queue labels.
ZEREMOTE (-67): Remote
call not implemented - Explanation:
Some ZCOM API calls do not support remote node operations.
This error is returned if a ZCOM routine is called with parameters
that require remote node access, but that routine does not support
remote node operations. - Action:
Correct the application source code.
ZEPQNO (-68): Bad physical
queue number - Explanation:
The zsetql routine
is used to set the queue limit for a physical terminal queue, but
an illegal queue number was specified. Refer to zsetql(3x) for more information. - Action:
Correct the application source code.
ZEZCOMREV (-69): ZCOM
software not compatible - Explanation:
The ZCOM software revision code is made up of four numbers.
The first two numbers are the major code and the last two numbers
are the minor code. The major code indicates major releases or substantial
changes that require software re-compilation and re-linking. The
minor code indicates small bug fixes or small enhancements. Most
ZCOM routines and utility programs compare the major revision codes
between each other and reject with this error if they do not match.
This error indicates software inconsistency between programs or
modules. - Action:
Re-compile or re-link the offending program or module. If
the problem persists, contact your HP support representative.
ZEONELTT (-70): Can't
remove the last LTT - Explanation:
The zltmg routine
requires the source terminal to be moved or removed to have other
terminals in its original group (hence its original group will not
be diminished after the move). This error is returned when the terminal
to be moved or removed is the only terminal in its group. - Action:
Correct the application source code.
ZEIFDOWN (-71): Interface
card not usable - Explanation:
This error occurs when a call is made to access
a Mux card directly whose state is marked as unusable (e.g. too
many failures, hardware problem). For example, calling the zport routine to configure a port
in a bad Mux card. - Action:
Replace the bad Mux interface card.
ZENOLS (-72): Logical
storage not allocated - Explanation:
This error is returned when zltstore is
called with the no-allocate bit (ZCOM_ZLTSTORE_NA) set, but the specified
storage label has not been previously defined. This error indicates
that the caller is trying to access a logical data storage that
does not exist. - Action:
Correct the application source code.
ZENOCARD (-73): Interface
card absent - Explanation:
Usually reported by the ZCOM subsystem program or driver
when it tries to communicate with a Mux interface card defined in
the TTGEN configuration file that has not been physically installed
in the computer. This may also be cause by incorrectly specifying
the bus and slot numbers in the "Mux" statement
of your TTGEN configuration file. - Action:
Make sure that you have specified the correct bus
and slot numbers for all Mux cards defined in your TTGEN configuration
file. Verify that the defined Mux cards are actually installed in
their correct locations.
ZENAVL (-74): Terminal
is not available - Explanation:
Indicates the terminal ZLU being accessed is associated
with a Mux interface card that is not physically installed in the
system or is installed in the wrong backplane slot. - Action:
Make sure that you have specified the correct bus
and slot numbers for all Mux cards defined in your TTGEN configuration
file. Verify that the defined Mux cards are actually installed in
their correct locations.
ZENOTM (-75): Terminal
not found - Explanation:
In the terminal search routines, ptfind and ltfind,
if a terminal with the specified parameter is not found, this error
code is returned. - Action:
Correct the application source code.
ZEFILESYS (-76): File
system error, check errno - Explanation:
ZCOM requests are passed to the ZCOM driver via
a set of standard HP-UX device files. This error code is returned
when the system detects a generic file system error not directly
related to the ZCOM subsystem. The global variable errno carries the HP-UX file system error
code. - Action:
Examine the value of errno and
correct the problem as needed.
ZEMEMORY (-77): Not
enough memory to startup ZCOM - Explanation:
This error is also reported by ZMON at ZCOM subsystem
startup. This error indicates that the available ZCOM kernel memory
(specified by the zcom_mem_size parameter
in the system file used to build the kernel) is not large enough
to create the ZCOM subsystem specified in the TTGEN configuration
file. - Action:
The problem can be resolved by either increasing
the amount of memory available for the ZCOM subsystem, or by reducing
the amount of memory required for your configuration. The amount
of memory required for your configuration as specified in the ttgen configuration file can be determined
by running ttgen with the -s option, and looking at the total
size value which is reported at the top of the SYSTEM
INFORMATION section. To increase the amount of memory,
increase the size of the zcom_mem_size tunable
parameter (usually in /stand/system), rebuild
the kernel (using mk_kernel), and reboot. To reduce the amount of
memory required for your configuration, review the TTGEN configuration
file and tune the parameters in that file (for example, reduce the
value given in the Terminal-ZLU parameter). Refer to Appendix B - Tuning and Sizing in
the ACC Installation and Configuration Guide for
more tuning details.
ZEBRESET
(-78): System being reset - Explanation:
This error code is reported by ZMON at ZCOM subsystem
startup. Each indicates that the ZCOM subsystem is in an unexpected
state. If ZMON is aborted (or killed) abnormally, the ZCOM subsystem may
be left in an unknown state and this may cause these errors to occur
upon a system restart. - Action:
ZMON is usually able to cope with these errors automatically.
However, if it cannot, do a proper shutdown (that is, zmasterd stop or zmon stop) and restart the system this
error may occur. If the problem persists, contact your HP support
representative.
ZEIODESC (-83): Too
many io descriptors - Explanation:
When ziftcmd is
called with too many I/O descriptors specified, this error is returned.
Currently, the zifttcmd routine
is used only by ZCBUG and is reserved for internal use only. This
is an internal defect in the product.
ZEHLABLEL (-84): Bad
system header label - Explanation:
During ZCOM subsystem startup, ZMON reports this error
if it finds that the header label in ZCOM kernel memory is corrupt.
The occurrence of this error could be due to memory corruption or
a defect in the ZMON process. - Action:
Contact your HP support representative.
ZESENDER (-85): Bad
sender's ZLU - Explanation:
When data is to be sent and the mode selected could result
in a response being returned to the sender's ZLU, the ZCOM
subsystem verifies that the sending program ZLU is valid. If the
specified sender's ZLU is invalid, the ZCOM subsystem will
reject the request with this error. - Action:
Correct the application source code.
ZEINTR (-86): Interrupt
occurs while waiting - Explanation:
When suspended, most of the ZCOM routines are interruptible
by a signal. This error code is returned when a signal is detected.
In this case, the user's signal catching function is invoked
before the ZCOM routine returns with this error. Depending on the
action specified for each signal, a signal may cause a program to
terminate or may be ignored completely. - Action:
Correct the program to handle this exception condition.
ZEBPTR (-87): User
buffer access error - Explanation:
The ZCOM driver was unable to access the data buffer specified
in the call. This indicates the buffer pointer specified was illegal
or corrupt. - Action:
Correct the application source code.
ZEQFLUSH (-88): Queue
is being flushed - Explanation:
This error indicates the destination program or terminal
ZLU is being shut down and is not accessible. This could occur as
a result of shutting down the ZCOM subsystem while a program is
trying to access the ZLU. - Action:
Application dependent.
ZEDAMIO (-89): Problem
in I/O with DAM - Explanation:
This error indicates an inter-driver interface problem between
the LDM and DAM. Currently such problems are reported by more specific
error codes. This error code is not used but is reserved to report
general interface problems in the future. - Action:
Contact your HP support representative.
ZEAPPNO (-90): Bad
application number - Explanation:
The application number specified in the call is
out of range. - Action:
Correct the application source code.
ZESKEY (-91): Bad search
key - Explanation:
Whenever the search key specified in the ptfind routine is invalid, for example,
a bad search mode, bad byte offset or key length, this error is
returned. - Action:
Correct the application source code.
ZELTLINK (-92): Corrupted
LTT group linkage - Explanation:
This error is returned whenever the ZCOM subsystem discovers
an inconsistency in the group linkage of logical terminals. - Action:
Contact your HP support representative.
ZEORMLOOP (-93): OMX
receiver maps into a loop - Explanation:
When the ZCOM subsystem tries to deliver a data message
to the receiver for an outbound multiplexing terminal and finds
that the receiver ZLU is mapped into an infinite loop, this error
is returned. Normally, this should not occur. - Action:
Contact your HP support representative.
ZEORZLU (-94): OMX
receiver ZLU out of range - Explanation:
When the ZCOM subsystem tries to deliver a data message
to the receiver for an outbound multiplexing terminal and finds
that the receiver ZLU is invalid, this error is returned. Normally,
this should not occur. - Action:
Contact your HP support representative.
ZENOIFT (-95): Not
a defined ZCOM interface - Explanation:
This error is reported by ZMON when it issues requests
to a Mux interface card that is not defined in the TTGEN configuration
file. Normally, this should not occur and is probably caused by
internal software problem. - Action:
Contact your HP support representative.
ZENORSP (-96): No empty
response record - Explanation:
When the ZCOM subsystem processes a send-with-wait request
(for example, zsend with mode
8), it allocates a response record to keep track of the request
status. This error indicates all response records are in use. The number
of response records is not configurable and is set to the number
of program ZLUs by TTGEN. - Action:
Re-design and modify the application to use fewer send-with-wait
requests.
ZEPCOUNT (-97): Invalid
number of parameters - Explanation:
This error is returned only for Fortran ZCOM routines. Some
of the FORTRAN versions of the ZCOM routines allow a variable number
of parameters. The error parameter is used to specify how many parameters
are being passed into the routine for this instance of the call.
However, the value passed in did not meet the minimum number of
parameters required for this specific request. - Action:
Correct the application program.
ZENIDX (-98): Node
index out of range - Explanation:
The node entry index specified in the zinfo() call (mode 6) is out of range.
The index must be in the range of 0 ... (Node-Entry - 1). The value for Node-Entry is defined in your TTGEN
configuration file. - Action:
Correct the application program.
ZEBADDMA (-99): Error
in DMA completion - Explanation:
This error is returned whenever a DMA operation
has completed abnormally. In this particular case, for some unknown
reason the ACC Mux card has not transferred all of the data requested.
The DMA operation is complete, but the DMA quad count is non-zero. - Action:
If this message occurs frequently or unusual behavior is
exhibited by the X25/ACC subsystem, contact your HP support personnel.
This message may be symptomatic of failing hardware (either the
ACC Mux card or some component in your system) or a failure in the
Mux firmware.
ZEDAMBUSY (-104): DAM
has too many requests - Explanation:
This error is returned whenever the Device Adaptor Manager
(DAM) receives a LLIO request when the DAM is already processing
a previously issued LLIO request. The DAM can only handle one outstanding LLIO
request at any given point in time. Most likely this is a defect
in the LDM. However, it may be possible to generate this error using
ZCBUG. - Action:
If this message occurs frequently or unusual behavior is
exhibited by the X25/ACC subsystem, contact your HP support personnel.
This may be symptomatic of an internal defect in the product.
ZEGETMEM (-105): Can't
get kernel IO memory - Explanation:
This error is returned when the driver cannot get enough
kernel memory to accommodate a Mux interface command (ziftcmd, etc.) Currently, this feature
is used only by ZCBUG. - Action:
Use less copies of ZCBUG concurrently or increase
the amount of kernel I/O memory specified in the /stand/system file
(iomemsize parameter).
ZEUNIMP (-106): Function
not implemented - Explanation:
This error is returned when a call is made to an unsupported
ZCOM routine or a request is not supported by the current version
of ZCOM subsystem. Currently, only the zxcpt routine
is not supported and will have this error returned. - Action:
Correct the application source code.
ZEKZLU (-107): No wait
on kernel ZLU - Explanation:
This error is returned on a zread routine
with wait on a kernel ZLU, that is, a ZLU that is set up to return
data to a kernel function using the zsetkfunc routine. Routine zsetkfunc is callable only by the
kernel drivers. User programs should never try to read from a kernel ZLU. - Action:
Correct the application source code.
ZERNOBUF (-108): No
data buffers for remote requests - Explanation:
This error is returned when the ZCOM subsystem was unable
to allocate a buffer from its internal memory pool to process a
remote request from an application. - Action:
Check for abnormal buffer usage in the associated remote
system or increase the Buffer-Pool parameter
in the TTGEN configuration file on the remote system.
ZEDUPRCVR (-109): Duplicate
shared receiver - Explanation:
An attempt was made to set up a program ZLU as a shared
receiver for data or system events but the program ZLU had already
been set up as a receiver. This return code is a warning. The program
ZLU will be left as a shared receiver. - Action:
Correct the application source code.
ZEBAD_ECLASS (-110):
Invalid event class - Explanation:
This error is returned by the zevent_rcvr routine
when an invalid eclass parameter
value has been specified. - Action:
Correct the application source code.
ZEOBSOLETE (-111):
Function obsoleted - Explanation:
This error indicates that the function called has
been obsoleted and is no longer supported. In most cases, a replacement
function has been available for several releases. - Action:
Correct the application source code to use the replacement
function.
ZEIFTYPE (-112): Bad
Interface Type - Explanation:
This error is returned when the application specified an
unknown interface type. That is, the interface type was not ZCOM_ITYPE_Z7400A, ZCOM_ITYPE_Z7300A,
ZCOM_ITYPE_Z7200A, ZCOM_ITYPE_Z7340A or ZCOM_ITYPE_Z7350A. One of
these types must be specified (and must match the ACC card being
used). - Action:
Correct the application source code.
ZEZGLOBAL (-113): Error
accessing /dev/zglobal - Explanation:
This error is returned when there is a problem in opening
or writing to the /dev/zglobal device file. This device file is
used by all ZCOM APIs to communicate with the LDM. This error indicates
some problems occur in software installation, or HP-UX system corruption. - Action:
Check the file permission of the /dev/zglobal device
file. Reinstall ACC software or reboot the system if required. If
problem persists, contact your HP support personnel.
ZeBAD_HPA (-120): Bad
HPA in interface table - Explanation:
This error is returned when the DAM driver detects inconsistencies
between the hardware card it binds with and the HPA sets up in the
ZCOM interface table. This error indicates internal software incompatibility. - Action:
Check to make sure there is no problem in software installation,
re-install if necessary. If problem persists, contact your HP support
personnel.
ZeNOT_DISABLED (-121):
DAM is not disabled - Explanation:
This error is returned when the DAM receives a LLIO request
that is not valid when the Mux card has been placed into its normal
operating mode (e.g. when the DAM is in the HLIO mode). - Action:
Contact your HP support personnel.
ZeDMA_TIMEOUT (-122):
Mux timed out - Explanation:
When a request is issued to the DAM to perform a
hard reset of the ACC Mux card, the DAM expects to see a external
interrupt from the card to indicate the reset is complete. This
error is returned if the external interrupt does not arrive within
a reasonable period of time. Most likely the card has experienced
a serious hardware failure. - Action:
Run hardware diagnostics on the Mux card in question and/or
swap the card out. If this does not appear to be a hardware problem
and the failure persists, contact your HP Support Representative.
ZeCARD_NOT_READY (-124):
Mux not fully started up - Explanation:
This error is returned when the LDM issues a LLIO "READY" request
to the DAM without having successfully issued the correct sequence
of LLIO requests. - Action:
Contact your HP support personnel.
ZeNO_RESTART (-125):
Missing "RESTART" request - Explanation:
This error is returned when the LDM issues a LLIO "ACTIVATE" request
to the DAM without having successfully issued a "RESTART" LLIO
request first. - Action:
Contact your HP support personnel.
ZeNO_IFT_ADDR (-126):
Missing "ENABLE" request - Explanation:
This error is returned when the LDM issues a LLIO "RESTART" request
to the DAM without having first informed the DAM of its Interface
Table address using the LLIO "ENABLE" request. - Action:
Contact your HP support personnel.
ZeDAM_NOT_BOUND (-127):
DAM not bound to any hardware - Explanation:
This error is returned when a request is issued
to an instance of the DAM for which there is no physical hardware
bound to it. - Action:
Verify that the ACC Mux cards are correctly installed in
the backplane of your system. If the problem persist, contact your
HP support personnel.
ZeNOT_IN_LLIO (-128):
DAM is not in the LLIO mode - Explanation:
This error is returned when a LLIO "RESET" request is
issued while the card is in a normal runtime operating mode. This
command is not allowed without first running zmasterd
stop or zmon stop. - Action:
Run zmasterd stop or zmon stop before attempting to issue
a reset command.
ZeSTOPPED_BY_DISABLE
(-129): Request stopped by "DISABLE" - Explanation:
When the DAM receives a LLIO "DISABLE" request,
it will terminate any request in progress with this error code.
Typically this is due to running "zmon
stop" or "zmasterd
stop". - Action:
No action is necessary.
ZeBAD_RUNBP_RESP (-130):
Bad response from Mux firmware - Explanation:
After downloading the firmware onto the ACC Mux card,
the DAM instructs the card using a backplane command to begin executing
its firmware. This error is returned when that command has returned
an unexpected result (e.g. non-zero). There are many potential reasons
for this problem. These include a corrupt firmware download file,
an internal defect in the firmware itself, or some form of hardware
failure. - Action:
Run diagnostics on the card and verify that the firmware
file (located in /opt/acc/<card-type>/)
is not compromised in any way. If this message occurs frequently
or unusual behavior is exhibited by the ZCOM subsystem, contact
your HP support personnel.
ZeNO_PORTS (-131):
No defined ports on Mux - Explanation:
This error is returned by the DAM when it is asked
to initialize an ACC Mux card that did not have any ports defined
for it. This could be a defect in TTGEN but most likely was caused
by an incorrect TTGEN configuration file. - Action:
Correct your TTGEN configuration file.
ZeSIO_MAP_FAILED (-132):
Kernel sio_map() function failed - Explanation:
This error is returned when the DAM attempted to map
a host address range into an I/O virtual address range, as required
by the DMA hardware, and this mapping operation failed. This error
prevents the DAM from sending the transaction to the ACC card. - Action:
Contact your HP support personnel.
|
Printable version
