Defining a list structure for a region status server

The region status server pool is defined in the list structure for a coupling facility data table. You define the list structure in a coupling facility resource manager (CFRM) policy.

About this task

You must allocate storage in the coupling facility to store CICS® status.

CICS records the status of a CICS region in a coupling facility data table named after the CICSplex to which the region belongs. That table must belong to a CFDT pool that is named in the CICSplex definition for that CICSplex. The default name is DFHRSTAT. In each z/OS® image, there must be a region status server for each region status pool that will serve the CICS regions belonging to that CICSplex. A CICSplex data table contains one region status record for each region in that CICSplex.

Define the structure in the current coupling facility resource management (CFRM) policy by using the IXCMIAPU utility. For an example of this utility, see member IXCCFRMP in the SYS1.SAMPLIB library. An example of a policy statement for a region status server pool is shown in Figure 2.

You must authorize server access to the list structure. For details, see Authorizing server access to a list structure.

Procedure

  1. Specify the name of the list structure. The name is formed by adding the prefix DFHCFLS_ to your chosen pool name, giving DFHCFLS_poolname. The default pool name as implemented by CPSM is DFHRSTAT.
    You define and modify CICSplexes using the EYUSTARTCPLEXDEF view set. Using the CPLEXDEF detail view, you can modify the coupling facility (CF) tuning parameters for the region status (RS) server, which provide sysplex optimized workload routing.
    Note: You can also modify the default region status (RS) pool name that will be used by all regions in the CICSplex. When you do not to use the default name DFHRSTAT, you must change the name before starting any other regions in the CICSplex. CPSM will not prevent you from changing the pool name while the CICSplex is active. If you make a change while the CICSplex is active, all CMAS and MAS regions in the CICSplex must be restarted as soon as possible. Failure to do so can result in inconsistent data in the CPSM WLM views and WLM optimization is deactivated until all the regions in the CICSplex are restarted.
  2. Specify the size of the list structure. Although the record size and calculations shown in Figure 1 can be useful for your own information, you must use the IBM® CFSizer tool to calculate the INITSIZE and SIZE parameters. The CFSizer tool takes minimums into consideration, but the calculations in Figure 1 do not. Failure to get valid sizing parameters using the CFSizer tool could result in a CICS runtime failure and DFHCF0403, DFHCF0409, and DFHCF0481 messages.
    When using the CFSizer tool, select CICS Data Tables list structure and specify the following values:
    Maximum number of tables
    Specify the number of CICSplexes that you have defined in CPSM and that will be using Sysplex Optimized Workloads. This is usually a very low number.
    Average rounded record size
    40
    Total records
    Specify the total number of CICS regions that will connect to all CICSplexes.
    Target usage percent
    Use the default.
    Maximum expansion percent
    Use the default.

    You can also specify ALLOWAUTOALT(YES), which enables automatic changes in the ratio of elements to entries, to make better use of the space within the structure.

    Figure 1. Example: Calculations of required structures

    A region status record is approximately 40 bytes long.

    If PLEX1 contains 100 regions, PLEX2 contains 300 regions, and PLEX3 contains 1000 regions, the required structures are as follows:
    • Poolname = DFHRSTAT, Table name = PLEX1, 100 regions x 40 bytes = 4 000 bytes total
    • Poolname = DFHRSTAT, Table name = PLEX2, 300 regions x 40 bytes = 12 000 bytes total
    • Poolname = DFHRSTAT, Table name = PLEX3, 1000 regions x 40 bytes = 40 000 bytes total
  3. Specify the preference list of coupling facilities in which the policy can be stored.
  4. When you have updated the CFRM new policy with the new structure definition, activate the policy using the following MVS™ command:
    SETXCF START,POLICY,POLNAME=policyname,TYPE=CFRM

    Where policyname is the CFRM policy being started, for example, DFHCFLS_DFHRSTAT.

    Note that defining the CFRM policy statements for a list structure does not create the list structure. The structure is created the first time an attempt is made to connect to it, which occurs when the first coupling facility data table (CFDT) server that refers to the corresponding pool is started.

Example

Figure 2. Example definition of a list structure for region status servers
STRUCTURE  NAME(DFHCFLS_DFHRSTAT)
    SIZE(7168)
    INITSIZE(6144)
    PREFLIST(FACIL01,FACIL02)


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