How many CICSplexes are there in your enterprise?
When you have identified those CICS systems or regions in your enterprise that can be managed by CICSPlex® SM, your next task is to decide how many CICSplexes you want to define to CICSPlex SM, and which of your CICS systems is to belong to each CICSplex.
- The entire enterprise
- Each geographical location
- Each business unit within the enterprise, or
- Each existing TOR-AOR-FOR configuration, or
- Each processor
- Geographic area within the CICSplex
- Function, such as all CICS systems that are application-owning regions (AORs), file-owning regions (FORs), or terminal-owning regions (TORs)
- Application, such as the CICS systems serving as AORs, FORs, and TORs that are used by a specific application or group of applications
- Time period, such as all CICS systems that are normally active during specific hours of the day or night
- Each CICS system that is to act as a target for specific workload processing must be in the same CICSplex as the CICS systems acting as routing regions. (The routing regions and target regions associated with a CICSplex can be in the same or different MVS™ images.)
- CICS systems acting as the routing regions must be CICS® TS systems.
If you plan to use the logical scoping, resource management, or installation functions of BAS, keep a business application within one CICSplex.
If you plan to use CICS BTS, you should keep a BTS-set with one CICSplex.
- Decide to have a single CICSplex for the entire enterprise.
- Look for reasons why a single CICSplex might not be feasible.
- Confirm your decision.
- Step 1: Have a single CICSplex for the entire enterprise
- The majority of enterprises find that having a single CICSplex best suits their system
management goals. The CICSplex is the largest single entity that CICSPlex SM can manage. None of the CICSPlex SM definitions or specifications can cross a CICSplex boundary. Furthermore, CICSplexes are mutually exclusive. No CICS system can belong to more than one CICSplex. Therefore, having a single CICSplex for the enterprise brings several advantages. For example:
- Providing the greatest opportunity for sharing and reusing BAS, WLM, RTA, and monitoring specifications and definitions.
- Giving you the most flexibility in managing the CICS workload when using the CICSPlex SM workload routing functions.
- Giving a single system image (SSI) of the entire enterprise. Also, the CICS operator is able to have a complete view of the enterprise CICS resources from a single CICSPlex SM window. (Because any CICSPlex SM window can display data from only a single context—that is, a single CICSplex—multiple windows would have to be displayed in a multi-CICSplex environment.)
- Step 2: Look for reasons why a single CICSplex might not be feasible
- The single
CICSplex solution is not the best approach in every enterprise, either because implementation is not
possible, or because it does not accord with other system management goals.
Firstly, you must ask whether the organization of your enterprise lends itself to a single CICSplex. For example, if you have processors in different geographical locations, are there connections between those processors, or are they managed as separate entities, each with its own workload? If you have these separate units in your enterprise, it is likely that you will need to define multiple CICSplexes, and so manage the enterprise CICS systems as if they belonged to more than one enterprise.
Similarly, is your enterprise organized and run as multiple, separate business units? For example, if you are running a bureau that provides computing services to a variety of customers, the absolute separation of one set of regions from another, even in a single processor, might simplify other processes, such as security management, customer billing, or workload management. If you have similar reasons for wanting to keep the management of some regions entirely separate from the management of others, consider defining multiple CICSplexes instead of one.
If you have decided that you need to define more than one CICSplex, it is probably obvious to you already which CICS system or CICS systems should belong to each. If it is not, consider revisiting your decision to have multiple CICSplexes because it suggests that you are trying to erect artificial barriers. As a final check, ensure that the way you separate the regions is not disruptive to your other system management goals. For example, if you want to use CICSPlex SM WLM functions, both routing regions and the target regions to which they route transactions must belong to the same CICSplex, unless you are planning to customize the supplied dynamic routing program.
- Step 3: Confirm your decision
- When you have decided whether to have one CICSplex or many, check
your decision against these other considerations:
- Does your CICSplex organization mirror your enterprise organization? If your enterprise is structured as multiple, independent units, having multiple CICSplexes is probably the better approach. If it is structured as a single entity, the single-CICSplex solution is likely to be the more suitable.
- Does your decision conflict with your enterprise's plans, either for its business or its information systems? For example, if your enterprise currently operates as multiple, separate entities, are there plans to unify them?
- Is your proposed configuration as simple as it could be? For example, are you planning to define four CICSplexes when two would support your system management goals?
- If you are planning multiple CICSplexes, have you considered whether CICS system groups could be used to achieve your goals? CICS system groups, unlike CICSplexes, are not mutually exclusive. This can be an advantage or a disadvantage, depending on your reasons for having multiple CICSplexes.
Remember that you can alter your decision. Ideally, you will discover the best possible configuration at your first attempt. However, if you decide after a while that a different CICSplex configuration would be better, you can make the necessary changes.