Using RMF reports to analyze message buffer space

To determine whether the signaling service was unable to satisfy a message request, the Figure 1 provides the following columns:

REQ REJECT

Indicates the number of message buffer requests not satisfied due to message buffer constraints. This column occurs under several headings in the report:

OUTBOUND FROM sysname: Where it indicates the number of requests to send a message to a particular remote system that were rejected in a particular transport class.
INBOUND TO sysname: Where it indicates the number of times that XCF was not able to obtain an inbound message buffer in anticipation of receiving a new message.
LOCAL: Where it indicates the number of requests to send a message within the local system that were rejected in a particular transport class.

In the XCF Activity Report - Path Statistics shown in Figure 3, the following columns under the heading “INBOUND TO sysname” are useful:

FROM/TO DEVICE OR STRUCTURE: Which identifies the device number or structure of the inbound/outbound signaling paths that could not obtain message buffers.
FROM SYSTEM: Which identifies the name of the remote system that may have suffered performance degradation because the inbound signaling path could not obtain message buffers.
REQ IN: Which identifies the number of requests.
BUFFERS UNAVAIL: Which indicates the number of times that XCF was not able to obtain an inbound message buffer for the signaling path in anticipation of receiving a new message.

When requests for message buffers are rejected, determine whether the maximum amount of space that XCF is allowed to use for message buffers was too small to support the load (and therefore degrades system performance), or whether there was some unusual/failure condition that caused the limits on buffer space to be reached (in which case the limits performed their intended function because they prevented large amounts of storage from being obtained and further impacting the system).