IBM Support

PM58471: CEXCP01 WHEN PUBLISHER API IS ACTIVE AND LPAR IS A UNI-PROCESSOR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • - A loop in module CEXPC01 can occur when a publisher API client
    is active and the LPAR is a uni-processor. The API client is
      usually OMEGAMON for IMS. The client side of the API is
      attempting to obtain the asynchronous buffer lock which uses a
      spin type of management.
    - If the Publisher API is inactive and the event collection
      level is low (i.e. 0), CEX uses more CPU than it has to for
      this environment due to sending the event records to a common
      collection point where they are made available to the
      Publisher API clients. Filtering by event collection level is
      done at the common collection point.
    - Virtual storage exhausted message on ISPF dialog when
      monitoring Active Sessions
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Connect Extentions V2.2         *
    ****************************************************************
    * PROBLEM DESCRIPTION: A loop in module CEXPC01 can occur      *
    *                      when a publisher API client is active   *
    *                      and the LPAR is a uni-processor.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR is addressing the following issues:
    1. A loop in module CEXPC01 can occur when a publisher API
    client is active and the LPAR is a uni-processor. The API client
    is usually OMEGAMON for IMS. The client side of the API is
    attempting to obtain the asynchronous buffer lock which uses a
    spin type of management.
    2. If the Publisher API is inactive and the event collection
    level is low (i.e. 0), CEX uses more CPU than it has to for this
    environment due to sending the event records to a common
    collection point where they are made available to the Publisher
    API clients. Filtering by event collection level is done at the
    common collection point
    3. Virtual storage exhausted message on ISPF dialog when
    monitoring Active Sessions
    4. Storage is filled with control blocks with ID for TOKENCONN
    and FUNCACHE if ICON is in Port retry loop because another ICON
    has the same ports open.
    

Problem conclusion

  • The following changes have been made for the above issues:
    1. The buffer lock obtain process has been changed to issue a
    STIMER when the lock cannot be obtained. This should allow the
    API partner to be dispatched and free the lock so it can be
    obtained by the other partner.  This process is repeated a
    fixed number of times and if the lock cannot be obtained, the
    client is notified with a reason code of 'Lock busy'.  The
    Client can re-issue the READ ASYNCHRONOUS request again if
    desired
    2. The code is changed to filter the event records at the point
    of collection if the Publisher API is not active. This reduces
    the CPU used in sending all of the events to the common
    collection point where they will be discarded because they do
    not match the event collection level that is active.
    3. Corrected ISPF console code to fix memory leak when
    monitoring active sessions.
    4. Corrected module CEXTECL1 to not connect to the FUNCACHE if
    there already is a connection for the task
    
    After applying this fix, users should
    restart their IMS Connect Extensions system.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM58471

  • Reported component name

    IMS CONNECT EXT

  • Reported component ID

    5655K4800

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-02-17

  • Closed date

    2012-03-01

  • Last modified date

    2012-04-03

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

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

    UK76712

Modules/Macros

  • CEXACLN  CEXAPEQU CEXCONS  CEXCONSC CEXEVT01
    CEXEXRTR CEXIICB  CEXMAIN  CEXMAPI  CEXOPDRV CEXPC01  CEXTECL
    CEXTECL1 CEXTEOT  CEXVUSER H28S220J
    

Fix information

  • Fixed component name

    IMS CONNECT EXT

  • Fixed component ID

    5655K4800

Applicable component levels

  • R220 PSY UK76712

       UP12/03/07 P F203

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.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88S","label":"IMS Connect Extensions"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.0"}]

Document Information

Modified date:
22 October 2020