IBM Support

PM06402: ESSS UNABLE TO START. MULTIPLE DUMPS TAKEN. EYUXE0023E AND EYUXE0025E MAY BE SEEN

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are attempting to start your CMAS.  This is the first time
    you've started it after an IPL.  This causes the ESSS address
    space EYUX320 to be started as well.  You may experience a
    situation where the ESSS abends and the CMAS hangs and does not
    respond.
    .
    If the CMAS is canceled, cleanup of CPSM areas may not occur
    because the ESSS is responsible for that, but it too abended.
    In your SYSLOG you may receive multiple SVC dumps.  Some of the
    titles may be:
    .
    EYU9X320.CREATE.FAIL.DUMP
    EYU9X320.SYSTEM.FAILURE
    .
    And the following messages may appear:
    .
    EYUXE0025E ESSS and PC Routines Mismatch Encountered
    EYUXE0023E ESSS address space not created - EYUX320 address
    space
    abended
    .
    To recover from this you must IPL.
    .
    Additional Information:
    KIXREVRBD
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a CMAS start requires the creation *
    *                      of the ESSS address space (EYUX320), if *
    *                      the address space initialization        *
    *                      routine fails, for example because of a *
    *                      mismatch between the ESSS module        *
    *                      (EYU9X320) and the PC routines          *
    *                      (EYUTXEPC), and the CMAS is cancelled   *
    *                      before issuing the EYUXE0025 error      *
    *                      message and performing cleanup, then    *
    *                      invalid data structures may exist.      *
    *                                                              *
    *                      When the cause of the ESSS address      *
    *                      space initialization failure is         *
    *                      addressed, all subsequent CMAS starts   *
    *                      that attempt to create the ESSS address *
    *                      space will fail with message EYUXE0023E *
    *                      being issued.  The text of the message  *
    *                      will be:                                *
    *                                                              *
    *                        EYUXE0023E ESSS address space not     *
    *                                   created - EYUX320 address  *
    *                                   space abended              *
    *                                                              *
    *                      These failures will continue until the  *
    *                      system is IPLed.                        *
    ****************************************************************
    * 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.                               *
    ****************************************************************
    The first CMAS that starts on a system after IPL or after the
    EYU9XEUT utility was executed to terminate the ESSS address
    space, will start the ESSS address space.  If the ESSS address
    space initialization process fails, then module EYU9XECS is
    notified in the CMAS, issues message EYUXE0025E, and then cleans
    up any data structures that have been partially created during
    the initialization attempt.
    
    EYU9XECS has a recovery routine to protect against abends.  If
    the recovery routine is entered it will ensure that the data
    structure cleanup is performed.
    
    Due to a logic error in EYU9XECS, the recovery routine will not
    be driven if the CMAS is cancelled.  This results in data
    structure cleanup not being performed, and as a result
    subsequent ESSS address space initialization attempts will fail
    until the system is IPLed.
    

Problem conclusion

  • EYU9XECS has been updated to ensure that its recovery routine is
    driven for all abends, including those resulting from the cancel
    of the CMAS.
    

Temporary fix

  •             *********
                * HIPER *
                *********
    FIX AVAILABLE BY PTF ONLY
    

Comments

  • ž**** PE10/03/03 FIX IN ERROR. SEE APAR PM09000  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PM06402

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    50M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-29

  • Closed date

    2010-02-16

  • Last modified date

    2010-03-11

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

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

    PM06779 UK54408

Modules/Macros

  •    EYU9XECS
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK54408

       UP10/02/18 P F002

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:
11 March 2010