SNAX/HLS Diagnosis and Support Manual

SNAX/HLS Log Messages
C–12 104706 Tandem Computers Incorporated
process name : Request from process issuing process name rejected
because RECEIVE queue is full
Cause. There are too many requests currently in progress in the subsystem. The actual
number of requests that can be accommodated is specified by the RECEIVEDEPTH
configuration parameter. For more information, refer to the SNAX/HLS Configuration
and Control Manual.
Effect. An application request is rejected with file system error 30 (no LCB space).
Recovery. Examine the event log to determine whether error 30 was generated by the
file system or the subsystem. If the file system generated the error, reconfigure the
Tandem NonStop Kernel to increase LCB space, or reconfigure the application
environment to reassign processes to other processors. If the subsystem generated the
error, rebalance the process-to-processor mix or consider restarting SNAX/HLS with a
larger value (if possible) for the RECEIVEDEPTH configuration parameter.
process name : RESETSYNC from process process that issued RESETSYNC
on file number file number used by requeste r
Cause. SNAX/HLS received a RESETSYNC request from the indicated process. This
situation usually arises after an application program takeover in which the file was
opened in the backup (with a CHECKOPEN call), but the sync-block was never
checked.
Effect. All current operations initiated on the file that supplied the RESETSYNC
request are discarded. The state of any resources these requests were controlling are
undefined.
Recovery. The event may signal an expected application event following takeover, or it
may indicate that the application program is not checking the file controls after a
CHECKOPEN call.
process name : SPI request from process issuing request bad: Code
word not -28
Cause. A SPI request was sensed without the code word (-28) in the first two bytes.
Effect. The request is rejected, the command fails.
Recovery. It is likely that your application has destroyed a valid SPI buffer, has lost
track of where it is built, or is sending the wrong data to the command and control
interface.