Maximum frame size of token ring

This topic contains a few guidelines and tips for specifying the maximum frame size.

First, here is some background information to help you understand the reasons for the guidelines and tips.

Larger frames require less processing overhead than the same data that is divided up among many smaller frames. Therefore, the use of larger frame sizes can improve the performance of your system. However, the frame size that you select can be reduced if other entities within the communications path cannot support the frame size.

Maximum frame size fields:

You can use these fields to specify the maximum frame size (the parentheses show location of the field):

If you specify a maximum frame size in two or more of these fields, the system selects the smallest size. To ease the frame size configuration of your line and controller descriptions, use these guidelines:

Reduction of selected maximum frame size:

Other entities within the communications path can reduce your maximum frame size if they cannot support it. Some of these entities are:

Solution:

If negotiation does not produce a common frame size, a frame reject (FRMR) condition occurs, and your system sends message CPA58E2 to message queue QSYSOPR. If you cannot change the frame size of the other entities, use an acceptable maximum frame size value in your line or controller description.