– Provided for lock structures only: GLYPH<129> z/OS V2.2 SPE with PTFs for APAR OA47796 GLYPH<129> Db2 V12 with PTFs GLYPH<129> Most performance-sensitive structures for duplexing – Benefit/Value: GLYPH<129> Db2 locking receives performance similar to simplex operations GLYPH<129> Reduces CPU and CF link overhead GLYPH<129> Avoids the overhead of synchronous protocol handshakes on every update GLYPH<129> Duplexing failover much fa ster than log-based recovery – Targeted at multi-site clients who run split workloads at distance to make duplexing  lock structures at distance practical. GLYPH<SM590000> CF Processor Scalability: – CF work management and dispatcher changes to allow improved efficiency as  processors are added to scale up the capacity of a CF image. – Functionally specialized ICF processors that operate for CF images having more than  a threshold number of dedicated processors defined for them: GLYPH<129> One functionally specialized processor for inspecting suspended commands.  GLYPH<129> One functionally specialized processor for pulling in new commands. GLYPH<129> The remaining processors are non-specialized for general CF request processing. – Avoids many inter-processor contentions that were associated with CF dispatching. GLYPH<SM590000> Enable systems management applications to collect valid CF LPAR information through  z/OS BCPii: – System Type (CFCC) – System Level (CFCC LEVEL) – Dynamic Dispatch settings to indicate CF state (dedicated, shared, and thin interrupt),  which are useful when investigating functional performance problems z14 ZR1 systems with CFCC Level 22 require z/OS V1R13 with PTFs or later, and z/VM  V6R4 or later for guest virtual coupling. To support an upgrade from one CFCC level to the next, different levels of CFCC can be run  concurrently while the CF LPARs are running on different servers. CF LPARs that run on the  same server share the CFCC level. z14 ZR1 servers (CFCC level 22) can coexist in a sysplex with CFCC levels 20 and 21. The CFCC is implemented by using the active wait technique. This technique means that the  CFCC is always running (processing or searching for service) and never enters a wait state.  This setting also means that the CF Control Code uses all the processor capacity (cycles)  that are available for the CF LPAR. If the LPAR that is running the CFCC includes only  dedicated processors (CPs or ICFs), all processor capacity (cycles) can be used. However,  this configuration can be an issue if the LPAR that is running the CFCC also includes shared  processors. Therefore, enable dynamic dispatching on the CF LPAR.  Starting with CFCC Level 19 and Coupling Thin Interrupts, shared-processor CF can provide  more consistent CF service time and acceptable usage in a broader range of configurations.  For more information, see 3.9.3, “Dynamic CF dispatching” on page 113. 112  IBM 14 Model ZR1 Technical Guide