Configuring the Network › SNA Considerations › Specify Pacing and Performance › Secondary Receive Pacing (SRCVPAC)

Secondary Receive Pacing (SRCVPAC)

Use Secondary Receive Pacing to perform session pacing between the following:

• The NCP boundary function and the SLU (session with link‑attached peripheral nodes)
• The PLU and the SLU (session with a locally attached LU in a single‑domain environment)
• The VTAM boundary function and the SLU (cross‑domain session with a locally attached node)

Pacing is used for OUTBOUND (PLU to SLU) traffic only. Specify a non‑zero value in the SRCVPAC field of the logmode entry to override all other Secondary Receive Pacing values.

Coding this value as 0 in the logmode SRCVPAC field indicates the usage of the value coded in the PACING parameter for the LU. If this is a session with a locally attached device in a single‑domain network, the value coded in the VPACING parameter on the LU definition is used. If these parameters are not coded in the LU definition and the logmode value is set to 0, the default value of 1 is used.

If no pacing is used for this stage, 0 must be coded in both the logmode SRCVPAC and the LU PACING definitions. If the session is with a locally attached node in a single‑domain environment, the VPACING parameter must be set to 0 in the LU definition, or the session is not established. For more information, see the following boundary function example.