Identifying system groups

You can identify one or more subsets of the CICS systems within a CICSplex as a CICS system group, which can be manipulated as a single entity and independently of the rest of CICSplex.

For example, if you define a CICSplex made up of TOR, AOR, and FOR CICS® systems, you might want to define the AORs as a CICS system group, so that you can use a single CICSPlex® SM command to make changes to, or request data from, all CICS systems in that category.

This section gives some suggested CICS system groups for the example configuration:
CICSplex 1
  • Group 1: TOR 1 and TOR 2
  • Group 2: AOR 1 through AOR 5
  • Group 3: FOR 1
  • Group 4: All CICS systems on System A
  • Group 5: All CICS systems on System B
  • Group 6: All CICS systems on System C
  • Group 7: Group 4 and Group 5
  • Group 8: All CICS systems in CICSplex 1
CICSplex 2
  • Group 1: TOR 3
  • Group 2: AOR 6 through AOR 9
  • Group 4: All CICS systems on System E
  • Group 5: All CICS systems on System G
  • Group 6: Group 4 and Group 5
  • Group 7: All CICS systems in CICSplex 2

Notice that Group 7 in CICSplex 1 and Group 6 in CICSplex 2 comprise of other groups. Defining groups within groups is very efficient, both for you (because it means less effort) and for CICSPlex SM.

Group 8 in CICSplex 1 and Group 7 in CICSplex 2 include the same set of CICS systems as the CICSplex to which it belongs. These are often useful groups to define because the scope value (as specified for a monitor specification, for example) can be a CICS system or a CICS system group name only: it cannot be the name of a CICSplex.

This is merely an initial list of system groups. It is likely to be added to (or altered) when BAS, WLM, RTA, and monitoring requirements are identified.

You can identify one or more subsets of the CICS systems within a CICSplex as a CICS system group, which can be manipulated as a single entity and independently of the rest of CICSplex. For example, if you define a CICSplex made up of TOR, AOR, and FOR CICS systems, you might want to define the AORs as a CICS system group, so that you can use a single CICSPlex SM command to make changes to, or request data from, all CICS systems in that category.

Figure 1. Identifying the CICSplexes. The example enterprise operates as two discrete units: the first three MVS images process a different workload from the remaining two, and there is no sharing of resources between those two groups. Accordingly, the enterprise CICS systems are to be divided between two CICSplexes. CICS systems that cannot be managed by CICSPlex SM (the CICS/400 systems, in the example) have been shaded.
The map shows the following systems: System A is an z/OS system with a TOR and two AORs. System B is an z/OS system with a TOR, a AOR and a FOR. System C is a z/OS system with two AORs. System E is a z/OS system with two CICS AORs and a TOR. System F is a z/OS system with two AORs. The CICS regions from System A, System B and System C belong to CICSplex 1. The CICS regions from System E, and System F belong to CICSplex 2.
Alternatively, you could define a single group for any of the following:
  • Particularly heavily loaded CICS systems
  • CICS systems that have different security requirements from the other CICS systems in the CICSplex
  • CICS systems in which particular applications run

CICS system groups, unlike CICSplexes, do not have to be mutually exclusive: a CICS system can belong to any number of groups within a CICSplex. However, because the CICS system group is a subset of the CICSplex, a system group cannot cross CICSplex boundaries.



eyue3bz.html | Timestamp icon Last updated: Sunday, 4 June 2017