Initial IT configuration

This section shows the starting point of the environment used in this scenario.

Figure 1. Initial configurationThe diagram shows two logical partitions (LPARs), in which CICS workload is running. LPAR 1 contains the maintenance CMAS and WUI. Both LPARs contain routing regions (TORs) that are connected to a number of target CICS regions (AORs).

To streamline the diagrams, connections between LPARs are not shown.

There are two logical partitions (LPARs), with a shared CICS system definition file (CSD):

LPAR 1 is running CICS TS for z/OS and CICSPlex SM V4.2. It has:
  • Two CICPlex SM address spaces (CMAS), one of which is the maintenance CMAS. The CMAS on this LPAR connects to both the maintenance point CMAS and the CMAS on LPAR 2.
  • Three terminal-owning regions (TORs). These are linked to application-owning regions (AORs) in LPAR 2.
  • A WUI server.
  • Ten application-owning regions (AORs). These are linked to terminal-owning regions (TORs) in LPAR 2.
LPAR 2 is also running CICS TS for z/OS and CICSPlex SM V4.2. It has:
  • One CICSPlex SM address space (CMAS). This connects to the two CMAS on LPAR 1.
  • Three terminal-owning regions (TORs). These are linked to application-owning regions (AORs) in LPAR 1.
  • Ten application-owning regions (AORs). These are linked to terminal-owning regions (TORs) in LPAR 1.

Both sets of TORs are defined with the same z/OS Communications Server generic resource. This means that, when the regions are shut down on one LPAR, the work should transfer to the regions on the second LPAR. CICSPlex SM can pass work that comes in to a TOR to any available AOR. This means that, each TOR connects to every AOR.



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