ACC Error Guide

ZCOM Driver Log Messages
ZCOM Driver Messages
Chapter 5 89
zcom 00102: Flushed <#> message(s) on closing ZLU <#>
Explanation: When a ZLU is to be closed or mapped (to another
ZLU), if the LDM finds some pending messages queued
on that ZLU, it flushes the queue and releases all
buffers to the buffer pool. These messages are reported
when this happens.
Action: None needed, this is an informational message.
zcom 00103: Flushed <#> message(s) on mapping ZLU <#>
Explanation: See “zcom 00102: Flushed <#> message(s) on closing
ZLU <#>.”
zcom 00111: Can’t get free buffer: corrupted free buffer at <#>
Explanation: This error is reported by the buffer pool manipulation
routines when they detect a data corruption problem in
the buffer header linkages. This is a serious problem,
most likely due to an internal defect in the product
(although this could also be caused by a defect in
another HP-UX or customer supplied kernel module).
The ZCOM subsystem will not function properly if this
occurs.
Action: You should immediately shutdown the ZCOM
subsystem (using zmon stop) and then restart it again.
This will correct the ZCOM data structure corruption
problems and restore the ZCOM subsystem to a normal
operating state. If other HP-UX subsystems are
experiencing problems, you may wish to reboot the
system. If the problem persists, contact your HP
Support Representative.
zcom 00112: Bad buffer returned to pool at <#> (flag <#>)
Explanation: See “zcom 00111: Can’t get free buffer: corrupted free
buffer at <#>.”