SNAX/HLS Diagnosis and Support Manual

SNAX/HLS Log Messages
104706 Tandem Computers Incorporated C–17
session name : No memory for RU, RU will be discarded
Cause. Memory congestion might result because the rate at which the messages are
arriving exceeds the rate at which the messages are being processed by the program.
Another reason for memory congestion is that the copy of SNAX/HLS is heavily
loaded.
Effect. The session is terminated.
Recovery. You should check whether or not receive pacing is being used and, if not,
whether or not you can introduce it. You should make sure that the pacing values are
not too big, reducing them if failures continue to occur.
You can also try to make more memory available to SNAX/HLS, either by directing
the process to a less-congested disk for swapping or by using the DATAPAGES
configuration parameter.
You can also try redistributing the load to other copies of SNAX/HLS.
session name : Receive data overrun, request will be discarded
Cause. The partner is sending data faster than your application can handle it.
Effect. The session is terminated.
Recovery. This might indicate that there is a flaw in your protocol—in particular, that
no flow controls are in effect. It might also indicate that pacing might have to be
introduced, or that the pacing window might have to be reduced to a smaller value.