IBM Support

PH00673: Controlling CPSM Dataspaces for extremely large CICSPlex implementations

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This APAR is being opened to document issues related to
    controlling CPSM Dataspaces for very large CICSPlex
    implementations.
    .
    Additional Symptom(s) Search Keyword(s): KIXREVGJT
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CPSM users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: In a very large CICSPlex SM             *
    *                      implementation, a CMAS terminates       *
    *                      with message                            *
    *                      EYUXC0023S applid Maximum data cache    *
    *                      limit has been reached for BAS cache.   *
    ****************************************************************
    The BAS component of CPSM maintains a cache list
    ( BPLX_RSET_LID ) which is used to control the installation
    of CICS resources into regions during MAS initialisation.
    In a very large CICSplex, the size of this list could grow to
    occupy a significant fraction of a single data space. The list
    must be held in contiguous storage, so can become difficult to
    modify or to extend.
    .
    Each CMAS maintains a BAS data cache, consisting of two data
    spaces. Storage constraint or fragmentation issues within
    those data spaces may mean that the list cannot be extended
    further, and attempts to do so (for example if new regions
    are added) may cause a CMAS to terminate with messages
    EYUXC0023S <applid> Maximum data cache limit has been
               reached for BAS cache.
    EYUXC0024S <applid> The CMAS is terminating due to a
               previous error with the Cache component.
    .
    Additional Keywords: msgEYUXC0023S msgEYUXC0024S
    

Problem conclusion

  • A new CICSPlex SM system parameter (EYUPARM) has been added
    to address this issue. This allows CPSM to allocate more
    that two data spaces to each data cache:
    .
     CACHEDSNUM(value | 2)
    .
      Specifies the number of data spaces that this CMAS creates
      for each CICSPlex SM component. At least 1MB is allocated in
      each data cache when the data space is created.
      The value must be in the range 1 to 8. The default value is 2.
    
      You can change this parameter only on a CPSM CMAS cold start.
      Normally, do not change this parameter unless advised to do
      so by IBM Support.
    .
    The CPSM dump formatter for the cache component (EYU9dnnn 'CHE')
    has been updated to print more digits for the number of
    elements in a cache list.
    .
    Any user with a need to increase the CACHEDSNUM value must
    restart the CPSM ESSS (Environment Services System Services)
    subsystem address space (EYUXnnn) after applying the PTF for
    PH00673, to activate the ESSS updates.
    An ESSS restart is not required if the CACHEDSNUM value is
    not increased.
    In either case, after the ESSS on an MVS image has been
    restarted with this update applied, all connecting CMAS, MAS
    and API regions on that MVS image must also have this update
    applied before attempting to reconnect.
    .
    The following topics in the IBM Knowledge Center will be
    updated:
    - CICSPlex SM system parameters
    - Managing CMAS restarts
    - Specifying each CMAS correctly in IEASYSxx
    - CICSPlex SM auxiliary storage usage
    .
    The following new messages will be added:
    EYUXC0026
    @EYUXC0026S <applid> CMAS warm restart with EYUPARM
                CACHEDSNUM(<parmval>), conflicts with previous
                value (<prevval>). CMAS is terminating.
    .
    Message Explanation:
     The CMAS performed a CPSM warm start because the shared data
     spaces existed when the CMAS was restarted.  The CACHEDSNUM
     EYUPARM value must be equal to the previous value.
    System Action:
     The CMAS terminates abnormally.  A user trace record is written
     to the CICS trace data set.
     Message EYUXL0112E will subsequently be issued.
    User Response:
     If the new CACHEDSNUM EYUPARM value is not required, the CMAS
     can be restarted successfully by setting the CACHEDSNUM EYUPARM
     to the previous value.
     If the new CACHEDSNUM EYUPARM value is required, then the CMAS
     must be CPSM cold started.  That is, the CMAS and all directly
     connected MASes and batch API programs must be terminated at
     the same time so that both the private and shared data spaces
     are terminated. Then the CMAS can be restarted.
     If the problem persists, collect the exception trace
     records and complete CMAS job output and contact your
     IBM Support Center.
    .
    EYUXC0027
    EYUXC0027I <applid> Data Cache initialization will be
               performed <start_type>
    .
    Message Explanation
     This indicates whether a CPSM CMAS warm or cold start will be
     performed.
     When a CMAS starts, if no data spaces that the CMAS used the
     last time it was active still exist, the start is a CPSM CMAS
     cold start; if such data spaces exist, the start is a
     CPSM CMAS warm start.
     Note that there is no way to deliberately specify a CPSM cold
     or warm start. The CICS system initialization parameter
     START has no effect on determining whether the restart of
     a CMAS is a CPSM CMAS cold or warm start.
     For further information on CPSM CMAS restarts refer to
     Managing CMAS restarts in Administering CICSPlex SM.
    System Action:
     None
    User Response
     None
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH00673

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    90M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-18

  • Closed date

    2018-11-09

  • Last modified date

    2018-12-12

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

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

    UI59603 UI59604 UI59605

Modules/Macros

  • CJA9XLRV CJA9XLRW CJB9XLRV CJB9XLRW CJC9XLRV CJC9XLRW CJD9XLRV
    CJD9XLRW CJE9XLRV CJE9XLRW CJF9XLRV CJF9XLRW CJG9XLRV CJG9XLRW
    EYU0DVCF EYU0UCIN EYU0XCIN EYU0XZPT EYU0XZSD EYU9D520 EYU9D530
    EYU9D540 EYU9DBG1 EYU9X520 EYU9X530 EYU9X540 EYU9XLBE EYU9XLRV
    EYU9XLRW EYUMCXCC EYUMCXCE EYUMCXCK EYUTXEPC
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R00M PSY UI59604

       UP18/11/15 P F811

  • R10M PSY UI59605

       UP18/11/15 P F811

  • R90M PSY UI59603

       UP18/11/16 P F811

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
12 December 2018