In the XCF Activity Report - Usage by Member under the heading labeled “MEMBERS COMMUNICATING WITH sysname”, are counts of messages sent to and received from remote systems in the sysplex. The name of the group and member and the remote system on which the member resides are identified, respectively, under the columns GROUP, MEMBER, and SYSTEM. The column “REQ FROM sysname” provides the count of messages sent by one or more members on system “sysname” (the system on which the data was collected) to the indicated member (that resides on the remote system). The column “REQ TO sysname” provides the count of messages sent to one or more members on system “sysname” (the system on which the data was collected) by the indicated member (that resides on the remote system).

Use your historical data to predict what signaling resources will be needed as changing workloads impact the remote signaling performed by these groups. For example, you might predict that additional signaling paths will be required at some point in the future to provide sufficient signaling capacity. Or you might determine that fewer signaling paths would be needed if the members of the remote system were moved to the local system or if some workload that uses services provided by the group were moved to the local system. You might not always be able to move a group member because the multisystem application may not have been structured to permit this kind of placement of members.

You can use the XCF Activity Report - Path Statistics to watch the “BUSY” and “AVAIL” counts on a signaling path. If “BUSY” grows relative to “AVAIL” over time, it suggests that the message traffic workload is increasing. You might want to add additional signaling paths to maintain signaling performance.

In the XCF Activity Report - Usage by Member under the heading labeled "MEMBERS ON sysname", are counts of messages sent and received by each member on system “sysname”, the local system that collected the data. The name of the group and member is identified respectively under the columns GROUP and MEMBER. The column “REQ OUT” indicates the number of messages sent by the member. The column “REQ IN” indicates the number of message received by the member. Use this data to determine which members on the local system are responsible for most of the message traffic.

If there is only one member per group on each system, you might be able to determine the precise message traffic patterns between particular group members. However, this is not possible to do in the general case.