SNAX/HLS Diagnosis and Support Manual

SNAX/HLS Log Messages
104706 Tandem Computers Incorporated C–13
process name : SPI request from process issuing request bad: Invalid
OCCURS value
Cause. A SPI message was received with a byte count that cannot occur in a well-
formed request message. It is possibly longer than the buffer transmitted, an odd
number of bytes, or less than the smallest conceivable value for a valid request image.
Effect. The request is rejected and the command fails.
Recovery. Correct the byte count and reissue the corrected command. If the problem
persists, gather the information discussed at the beginning of Section 1, "Problem
Determination" and contact your Tandem analyst.
process name : SPI request from process issuing request bad: Message
short
Cause. A SPI request was received that was too short to be a valid request.
Effect. The request is rejected and the current command fails.
Recovery. Correct the request. If the SPI request is correct, gather the information
described at he beginning of Section 1, "Problem Determination" and contact your
Tandem analyst.
process name : SPI request from process issuing request bad: No
header
Cause. No SPI header was found.
Effect. The request is rejected and the command fails.
Recovery. Correct the request. If the request is correct, gather the information
discussed at the beginning of Section 1, "Problem Determination" and contact your
Tandem analyst.
process name : SPI request from process issuing request bad: Not a
command message
Cause. A SPI command was sensed that was not a command buffer.
Effect. The request is rejected and the command fails.
Recovery. Correct the request. If the request is correct, gather the information
discussed at the beginning of Section 1, "Problem Determination" and contact your
Tandem analyst.