The Workload Manager must know the names of the server groups between which workload can be managed, and the names of the CICS servers that belong to each server group. The Workload Manager can also (optionally) know the names of the programs that can run in each server group.
You supply this information using the Configuration Tool which produces the appropriate entries in the configuration file. For more information see Configuring the Windows Workload Manager.
The following table shows the information that the Workload Manager requires. To enable workload management the Client daemon must be able to correlate CICS servers against the server groups to which they belong.
Server group | CICS server |
---|---|
GROUP1 | CICS1 CICS2 CICS3 |
GROUP2 | CICS4 CICS5 |
GROUP3 | CICS6 |
For example, connections from a specific client to CICS2, CICS4, and CICS6 would be valid but connections to CICS1, CICS3, and CICS5 would not be valid because CICS1 and CICS3 belong to the same server group.
Not all CICS programs need be available on all possible server groups. The Workload Manager knows the name of the program that the client request is for, and can select, from a subset of all server groups, those server groups on which a particular program is defined. The Workload Manager also has knowledge of a set of server groups where undefined programs can be routed.
For example:
Program | Server group |
---|---|
PROG1 | GROUP1 GROUP2 GROUP3 |
PROG2 | GROUP1 GROUP3 |
PROG3 | GROUP2 |
When the Workload Manager receives requests for programs which have not been defined in the configuration file, the round robin algorithm distributes the requests across all server groups and the biasing algorithm uses the default server