MAX_RECEIVE_PACING_WINDOW

Required? No
Keyword Type Unsigned number
Default 0 (no limit)
Range 0–63
Multiples Allowed? No, only one for each MODE keyword
   RECEIVE_PACING_WINDOW = (
      @TYPE = UNSIGNEDNUMBERKEYWORD
      @RANGE = 0,63
      @REQUIRED = 1
      @DEFAULT = 0
    )
 

The PACING_WINDOW parameter indicates to the partner logical unit (LU) how many request units (RUs) it can send before receiving a pacing response. The value is an integer in the range 0–63 for MAX_RECEIVE_PACING_WINDOW.

MAX_RECEIVE_PACING_WINDOW is used with adaptive pacing to limit the maximum pacing window, in order to prevent remote local buffers from overrunning.

This parameter is not required, and it is used only for adaptive pacing. However, Communications Server and Personal Communications always use adaptive pacing, unless the adjacent node specifies that it does not support it.

This parameter is required, but it is used only for adaptive pacing. However, Communications Server and Personal Communications always using adaptive pacing, unless the adjacent node specifies that it does not support it.

The default is 0, which means that there is no adaptive pacing limit. Note that a nonzero value cannot be less than the RECEIVE_PACING_WINDOW.

Session pacing helps to prevent local buffers from overrunning. The receive pacing window size is the session pacing limit for sessions in this mode. The actual value used may be negotiated between the nodes when the session is started.

For fixed pacing, this value specifies the receive pacing window. For adaptive pacing, this value is used as an initial receive window size. Communications Server always uses adaptive pacing unless the adjacent node specifies that it does not support it.