SNAX/APN Application Programming Manual

The SNALU Interface
SNAX/APN Application Programming Manual—420111-001
4-21
Pacing
The IBM Systems Network Architecture: Format and Protocol Reference: Architectural
Logic manual more fully describes these send and receive modes.
Pacing
Session-level pacing allows an LU to control the rate at which it receives requests on a
normal flow. Such pacing is typically used when the sending LU is capable of
transmitting requests faster than the receiving LU can process them.
Pacing is described in the IBM Systems Network Architecture: Format and Protocol
Reference: Architectural Logic manual.
Terminating LU-LU Sessions
There are several ways to terminate LU-LU sessions:
•
The PLU can send an unsolicited UNBIND request to the SLU
•
The SLU can send an unsolicited UNBIND request to the PLU
•
The SLU can send a TERM-SELF request or a character-coded logoff message to
the PLU, causing the PLU to send an UNBIND request
•
In response to an operator command or upon detecting an irrecoverable error
condition, SNAX/APN generates two UNBIND requests (one sent to the PLU, one
sent to the SLU). The commands that can generate UNBIND requests are:
•
STOP LU, FORCED
•
ABORT LINE
•
ABORT PU
•
ABORT LU
•
ABORT SESSION
The first three of these are described in more detail in the subsequent two sections.
SNALU Application Terminates Session With Remote SLU
When the SNALU application is the PLU, it can terminate a session by sending an
UNBIND request to the remote SLU, as shown in Figure 4-6.
Note. It is recommended that SNALU applications implement pacing. Also, SNAX/APN does
not support the Pacing Indicator when using the CRT and ITI protocols.