Planning for the number of log structures

There are a number of points to consider when planning the definition of your coupling facility structures.

  • The CFRM policy allows a maximum of 255 structures for all purposes.
  • Allow a maximum of 512 log streams per structure.
  • Smaller structures are more quickly allocated, rebuilt, and recovered than larger ones.
  • It is good practice to keep the log streams for test CICS® systems and other systems not in regular use in structures separate from the structures holding the log streams of production CICS systems. This separation avoids the structure space available to production CICS systems being affected by structure usage of the test CICS systems.
  • It is good practice to keep the log streams for terminal-owning regions (TORs) in structures separate from those accommodating log streams for application-owning regions (AORs). In addition, keep log streams for file-owning regions in structures separate from those accommodating log streams for TORs and AORs.
  • Share structures between MVS™ images. If an MVS image or logger address space fails, and a surviving MVS image is using the same log stream structures, although not necessarily the same log streams, the surviving image is notified of the failure and can initiate immediate log stream recovery for the failing MVS.

    Recovery, otherwise, is delayed until the next time that a system attempts to connect to a log stream in the affected structures, or until the logger address space of the failing system is restarted.

    For example, in a 4-way sysplex comprising MVSA, MVSB, MVSC, and MVSD, you might have the CICS regions that normally run on MVSA and MVSB use structure LOG_DFHLOG_001, and the regions that run on MVSC and MVSD use structure LOG_DFHLOG_002. Thus, each MVS image has a partner to recover its log streams if MVS fails. If a structure fails, the two MVS images using the other structure can take over the workload. Also, if you have more than one coupling facility, allocate the system log structures to different coupling facilities. See Figure 1 for an illustration of this example.
    Figure 1. Sharing system logger structures between MVS images
    a diagram that repeats the example given in the previous paragraph.
  • Use the appropriate buffer size. The average buffer size (AVGBUFSIZE) defined for a structure must be close to the actual buffer size of the log streams using the structure. If it is not,usable space might be exhausted long before the structure is full.
    Important:
    1. z/OS dynamically tunes the element and entry ratio, so the value you specify for AVGBUFSIZE is less important than it was on earlier releases of MVS.
    2. You cannot update AVGBUFSIZE, like other structure definition attributes such as MAXBUFSIZE and LOGSNUM, unless you first delete the log streams in the structure definition.
  • Set MAXBUFSIZE to slightly less than 64 KB; for example, 64 000 is suitable. This number allows CICS to write the maximum size user record and allows coupling facility storage to be allocated in 256-byte units. If you allow MAXBUFSIZE to default, coupling facility storage is allocated in 512-byte units. This size can be wasteful of storage.

    If you set MAXBUFSIZE lower than 64 000 you gain no significant advantage as far as the use of storage is concerned.

  • Set a low value for the REBUILDPERCENT parameter in the CFRM policy for log structures used for CICS system logs.


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