IBM Support

PH64340: Updating BAS resource definitions takes excessively long

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You have an extremely large BAS table with millions of entries.
    Updating resource definitions in this table by any method takes
    an excessive amount of time, up to 30 seconds per update.
    
    
    This is due to a bug that causes CPSM to search the entire
    file every time a query is made.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM users                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When updating a BAS definition          *
    *                      via the WUI or the API there can be a   *
    *                      delay, with a lot of CPU usage before   *
    *                      the the update is performed.            *
    *                                                              *
    *                      The delay is more noticeable if the     *
    *                      number of items installed via BAS is    *
    *                      very large and the item is towards the  *
    *                      end of the BRSE table.                  *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF to all CMASes, in any order.   *
    ****************************************************************
    This issue would affect only systems using the support for
    large CICSPlex SM cache lists. Prior to release 6.2, only
    systems specifying feature toggle
    com.ibm.cics.cpsm.bas.largecicsplex=true would be affected.
    
    When looking for an item, such as a TRANDEF, towards the end of
    a large list of BAS installed items, the lookup code scans the
    BRSE list of all BAS installed items on all MASes, the B+ Tree
    code incorrectly starts to look for the required item(s) from
    the start of the list instead of using the index to find the
    first match.
    
    As a result the search for the list items takes a long time and
    uses a lot of CPU. The search still results in the correct items
    being found and processed.
    

Problem conclusion

  • EYU0XCLG, a module that sets up search patterns and drives the
    list search process, has been modified to correctly specify the
    decremented primary key when calling EYU0XCX3, the B+ Tree
    processing module, so that EYU0XCX3 can quickly find the start
    of the required records via the B+ Tree index instead of
    sequential scan.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH64340

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-11-27

  • Closed date

    2025-04-22

  • Last modified date

    2025-05-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PH64514 UO02890

Modules/Macros

  • EYU0UCLG EYU0XCLG
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R30M PSY UO02890

       UP25/04/25 P F504

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.6","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
02 May 2025