Chapter 98 SNAX‑HLS Messages

This chapter describes the messages sent by the SNAX/HLS subsystem. The subsystem ID displayed by these messages includes SNAX‑HLS as the subsystem name.

Events reported by the SNAX/HLS subsystem are divided into two classes: potentially critical events and noncritical events. Potentially critical events, such as the loss of a session or the termination of the SNAX/HLS process, are those for which the consequences could be serious. Noncritical events, such as the sending or receiving of a negative response, are less serious events that are likely to be handled by well‑written application programs.

Potentially critical events are indicated by “(BELL)” on the $0-controlled console and are highlighted in color in the OSM and TSM event viewers (on G-series RVUs) or displayed in a highlighted format on the ViewPoint operator console (on D-series RVUs).




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

proc-name: RDT must be a disk file, file = filename

proc-name

is the name of the SNAX/HLS process.

Cause An attempt was made to load a Resource Definition Table (RDT) file from a device other than disk.

Effect The attempt to load the file is abandoned. If the load is the result of program initiation, the SNAX/HLS program is terminated abnormally.

Recovery Use a disk file.

sess-name: SNAX buffer overload

sess-name

is the name of the session to which the message refers.

Cause The SNAX line handler has rejected an outbound request because of temporary memory congestion.

Effect Data is not lost.

SNAX/HLS treats this condition automatically. The rejected send request is retried, and the rate at which data is sent to this LU is slowed down. When the overload errors cease, the submission rate is increased. This adjustment is automatic inside the SNAX/HLS process and is invisible to the application, except for the slowdown of data.

Recovery If this condition persists and you are using SNAX/XF as the Tandem SNA access method, increase the size of the buffers available to the line handlers (the XPAGES parameter). If you are using SNAX/CDF as the Tandem SNA access method, increase the size of the DATAPAGES startup parameter. If this option is unavailable, you might want to redistribute your network to reduce the overloading of the line on which this logical unit (LU) resides.

proc-name: Customizer error.

proc-name

is the name of the SNAX/HLS process.

Cause This error message typically indicates one of the following conditions:

The customizer attempted to enlarge an outbound message beyond the 256-byte limit.
The customizer initialization routines attempted to allocate memory more than once.

Effect The SNAX/HLS process terminates abnormally.

Recovery The customizer routines should be corrected and relinked to SNAX/HLS.

sess-name: Invalid MU Received, MU = msg-unit

sess-name

is the name of the session to which the message refers.

Cause SNAX/HLS has received a message unit (MU) from the session partner that violates SNA protocol. The first 16 bytes of the message are presented.

Effect The defective MU is discarded, and the session is terminated immediately.

Recovery Inspect the MU, and determine whether it is malformed or represents a response unit (RU) that is not supported by SNAX/HLS, or that is in error because of the type of session. Taking SNAX/HLS traces for the session on which the MU was received may help you to isolate the problem.

sess-name: Attempt to send invalid MU, MU = msg-unit

sess-name

is the name of the session to which the message refers.

Cause SNAX/HLS has attempted to send a message unit (MU) that violates SNA protocol. The first 16 bytes of the message are presented.

Effect The defective MU is discarded, and the session is terminated immediately.

Recovery Inspect the MU, and determine whether it is malformed or represents a response unit (RU) that is not supported by SNAX/HLS, or is in error because of the type of session. Taking SNAX/HLS traces for the session on which an attempt was made to send the MU may help you to isolate the problem.

sess-name: Invalid response received, MU = msg-unit

sess-name

is the name of the session to which the message refers.

Cause This message indicates that SNA protocol has been violated. For example, a request with a definite response type 1 (DR1) was sent out and a response with a definite response type 2 (DR2) was received.

Effect The defective MU is discarded, and the session is terminated immediately.

Recovery Inspect the MU, and determine whether it is malformed or represents a response unit (RU) that is not supported by SNAX/HLS, or is in error because of the type of session. Taking SNAX/HLS traces for the session on which the MU was received may help you to isolate the problem.

sess-name: (-RSP) response received, MU = msg-unit, SNAERR = error-code

`error-code`	is the standard SNA error code.
`sess-name`	is the name of the session to which the message refers.

Cause A negative response has been received by the local application or by SNAX/HLS.

Effect If the session is being established, the establishment fails. If data traffic is active, the negative response is delivered to the application. This message is intended to provide an audit trail.

Recovery Typically, negative responses indicate either a mismatch of session-partner specifications (an incorrect profile specified to SNAX/HLS), protocol violations by the partner, or internal SNAX/HLS errors.

There are two circumstances that are likely to cause this situation: either the profile specified in a BIND or INIT-SELF record was incompatible with the device or gateway application, or the IBM subsystem or device was configured incorrectly.

If the negative response is not expected, you might have to perform error analysis by obtaining SNAX/HLS traces.

sess-name: (-RSP) sent, MU = msg-unit SNAERR = error-code

`error-code`	is the standard SNA error code.
`sess-name`	is the name of the session to which the message refers.

Cause A negative response has been sent by the local application or by SNAX/HLS.

Effect If the session is being established, the establishment fails. If data traffic is active, the negative response is sent to the partner. This message is intended to provide an audit trail.

Recovery Typically, a negative response indicates either a mismatch of session-partner specifications (an incorrect profile specified to SNAX/HLS), protocol violations by the session partner, or internal SNAX/HLS errors. Of course, negative responses may be perfectly normal if so dictated by the application-level protocol.

If the negative response is expected and is a frequent occurrence, you are advised to disable the publication of this message.

If the negative response is not expected, you may have to perform error analysis by obtaining SNAX/HLS traces. You can avoid this message if you carefully plan SNAX/HLS sessions.

sess-name: No memory for RU. RU will be discarded.

sess-name

is the name of the session to which the message refers.

Cause An inbound message was discarded because of memory congestion.

Memory congestion might result because the rate at which the messages are arriving exceeds the rate at which the messages are being absorbed 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 parameter.

You can also try redistributing the load to other copies of SNAX/HLS.

proc-name: RDT file filename has version mismatch.

proc-name

is the name of the SNAX/HLS process.

Cause An attempt was made to load or switch to an old RDT database.

Effect The load attempt is abandoned. If this error occurs at program startup, the process terminates abnormally; otherwise, the old RDT database remains in effect.

Recovery You probably need to recompile the RDT database using the HLSRDT program.

sess-num: Receive data overrun. Request will be discarded.

sess-name

is the name of the session to which the message refers.

Cause The number of inbound messages on a session exceeds 255.

Effect The session is terminated.

Recovery The partner is sending data faster than your application can handle it. This may indicate that there is a flaw in your protocol—in particular, that no flow controls are in. It may also indicate that pacing may have to be introduced, or that the pacing window may have to be reduced to a smaller value.

proc-name: Request for MAX^POCBS = max-pocbs and MAX^LUS = max-lus excessive. Current limits are: tcb-size*(MAX^POCBS) + pocb-size*(MAX^LUS+1) less than max-tbls bytes.

`max-pocbs`	conveys the configured value for the MAX^POCB parameter, reflecting the maximum number of opens SNAX/HLS can handle.
`max-lus`	is the configured value for the MAX^LUS parameter, reflecting the maximum number of logical units (LUs) that SNAX/HLS can handle.
`max-tbls`	is the upper limit, in bytes, on the amount of storage that can be dedicated to the combined open and LU table in SNAX/HLS.
`pocb-size`	is the size, in bytes, of each process opener control block (POCB) in the current implementation of SNAX/HLS.
`proc-name`	is the name of the SNAX/HLS process.
`tcb-size`	is the size, in bytes, of each task control block (TCB) in the current implementation of SNAX/HLS.

Cause The number of opens and sessions requested, while individually within legal bounds, collectively require the allocation of too much memory.

Effect SNAX/HLS terminates abnormally. Because this error is detected before the backup is started, no takeover occurs.

Recovery Correct the configuration parameters. This may require you to redistribute the load to additional copies of SNAX/HLS.

proc-name: Unexpected pacing response received.

proc-name

is the name of the SNAX/HLS process.

Cause An unexpected pacing response was received.

Effect The pacing response is discarded.

Recovery Informational message only; no corrective action is needed.