SFF client groups for a TCP/IP port

Introduction

The LST parameter Bnn_TCPIP_MAX_CLIENT_GROUPS enables you to enhance the throughput of a TCP/IP port by defining SFF client groups for the port. As a rule, one SFF client group is sufficient for normal product TCP/IP clients. However, in the event of heavy workloads on the various applications, the following values are recommended:

  • Web applications (e.g. BWE) – maximum of 5 SFF client groups
  • Agents (e.g. OSY) – maximum of 10 SFF client groups.

Client groups as solution

If you are using the BSA TCP/IP server, it is possible to create up to 26 SFF client groups (TCL groups) for a TCP/IP port. This not only takes the z/OS dispatcher control function into account, but also makes very efficient use of the internal SFF dispatcher control function, enabling throughput to be increased.

Defining client groups

A maximum of 26 client groups can be defined using LST parameter Bnn_TCPIP_MAX_CLIENT_GROUPS=xx (valid for all global ports) or Bnn_TCPIP_MAX_CLIENT_GROUPS_app=xx, (valid for all ports for the specified application app), where xx specifies the number of SFF client groups to be generated for the port. If more than 26 client groups are specified, the parameter is automatically reset to 26. The default is 1. When the product STC is started, the number of client groups specified here are defined.

Naming conventions for client groups

SFF client groups can be displayed by this operator command:

F stcname,TL

The name of the SFF client group is determined by the port and the application, and by the number of client groups that have been defined, for example:

No. of client groups

Name components

Description

Example

1 only

app_port

app = name of the application, e.g. OSY, BWE)

port = Application port as HEX (e.g. port = 64000 = FA00 HEX)

OSY_FA00

More than 1

appportb

app = name of the application, e.g. OSY, BWE)

port = Application port as HEX (e.g. port = 64000 = FA00 HEX)

b = Consecutive number represented by the letters A to Z.

OSYFA00A

Limitations

  • SFF Client groups can only be defined for the BSA TCP/IP server. They are not supported by the BSA Communication Integrator.
  • SFF client groups can not be modified dynamically using the BSA Service Manager during runtime of the STC.
  • If values for client groups are set too high, an increase in parallel processing could also lead to an increase in CPU usage.