IBM Support

PK47637: PERFM SLOW PERFORMANCE AFTER CMAS RECYCLE IN EXISTING CMAS NETWORK TIMEOUTS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Unpred- Unpredictable hangs or waits can occur due to the
    communication network lock being held by a task with a low
    dispatching priority in the CMAS.
    .
    If a CMAS is recycled in a large CMAS network, the recycled CMAS
    may experience any or all of the following symptoms.
    .
    - CMAS can go MAXTASK
    - CMAS can go SOS (Short-on-Storage) System under stress
      DFHSM0131 DFHSM0133
    - MASes may fail to connect - EYUNL0090W timeout MASINITTIME
    - CMAS repository synchronization failed EYUCP0205S
    - CMAS isolation EYUCP0023E EYUCP0024E
    - API program ENVIRONERROR TIMEOUT WUI timeout
    .
    Additional Symptom(s) Search Keyword(s): netlock dispatchable
    XLST priority 70 CHAP_TASK EYU0XLST slow hang hangs hung wait
    waits join connect fail fails failed workload wlm
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unpredictable hangs or waits can occur  *
    *                      due to the communication network lock   *
    *                      being held by a task with a low         *
    *                      dispatching priority in the CMAS.       *
    *                                                              *
    *                      If a CMAS is recycled in a large CMAS   *
    *                      network, the recycled CMAS may          *
    *                      experience any or all of the following  *
    *                      symptoms:                               *
    *                                                              *
    *                      - CMAS may go MAXTASK.                  *
    *                                                              *
    *                      - CMAS may go SOS (Short-on-Storage),   *
    *                        with CICS message DFHSM0131 or        *
    *                        DFHSM0133 issued.                     *
    *                                                              *
    *                      - MASes may fail to connect, with       *
    *                        message EYUNL0090W issued.            *
    *                                                              *
    *                      - CMAS repository synchronization may   *
    *                        fail, with message EYUCP0205S issued. *
    *                                                              *
    *                      - the CMAS may be isolated from the     *
    *                        CMAS network, with messages           *
    *                        EYUCP0023E and EYUCP0024E issued.     *
    *                                                              *
    *                      - EUI requests may time-out.            *
    *                                                              *
    *                      - API programs, including the WUI, may  *
    *                        receive time-outs, with a Response of *
    *                        ENVIRONERROR and a Reason of TIMEOUT. *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be restarted.  Note    *
    *                 that the restarts do not need to occur at    *
    *                 the same time.                               *
    ****************************************************************
       When a request is shipped from one CMAS to another, it may
    run under a task with the transaction ID of XLST.  The default
    priority of this task is lowered for these requests.  Depending
    upon how busy the CMAS is, this may result in these tasks not
    being dispatched in a timely manner.  This will not only affect
    these tasks, but it will also affect other tasks when the XLST
    task holds the communications lock.  This can lead to any of the
    symptoms indicated above.
    

Problem conclusion

  •    Method EYU0XLST (XLST) has been updated so that it will not
    lower its priority when it is executing a request shipped from
    another CMAS.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK47637

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    50M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-06-22

  • Closed date

    2007-07-06

  • Last modified date

    2007-08-03

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

    PK47310

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

    UK26832

Modules/Macros

  •    EYU0XLST
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK26832

       UP07/07/07 P F707

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":"3.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":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 August 2007