IBM Support

PH51320: CPSM WLM ROUTES NON-TERMINAL STARTS INTERMITTENTLY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Occasionally during startup dynamic transaction routing decides
    to use the internal EYU9WRAM instead of a customer's own
    version.
    
    This is down to a race condition between WLM initialisation and
    MAS heartbeat process. If WLMinit gets delayed and the heartbeat
    runs before the TOR is fully set up then heartbeat arbitrarily
    decides to use the internal EYU9WRAM. This is corrected a
    minute later by heartbeat.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CPSM users who run a customised version  *
    *                 of EYU9WRAM, the route selection module.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Occasionally, if the user has their own *
    *                      version of EYU9WRAM, a MAS will use the *
    *                      internal version at startup instead of  *
    *                      the customised version. This corrects a *
    *                      minute later.                           *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves         *
    *                 this APAR all CMASes and MASes must be       *
    *                 restarted to pick up the new code.           *
    *                                                              *
    *                 The restarts need not be performed at the    *
    *                 same time, however if systems are not        *
    *                 restarted at the same time, the following    *
    *                 rule applies:                                *
    *                                                              *
    *                 - Before a CMAS is restarted with the        *
    *                 updated code, the MASes that connect to it   *
    *                 must be running with the updated code.       *
    *                                                              *
    *                 If the CMAS is updated first then the        *
    *                 EYU9WRAM status will be set at MAS startup   *
    *                 and will not be modifiable without a MAS     *
    *                 restart.                                     *
    *                 This does not mean you cannot change your    *
    *                 own EYU9WRAM module, just that you cannot    *
    *                 change from the internal version to an       *
    *                 external version without a CICS restart      *
    *                 unless the MAS has the PTF applied.          *
    ****************************************************************
    There is an intermittent startup timing issue where the MAS
    heartbeat program runs before a MAS is fully initialised as a
    routing region. The MAS then sends an incorrect default WRAMLINK
    value to the CMAS as part of the EMSTATUS record. The CMAS then
    sets the WTOR_WRAM_LINK value based on this.
    

Problem conclusion

  • The code has been modified such that the MAS heartbeat program,
    EYU0NLHD, now asks the EYU0WNHD subprogram to check the status
    of the EYU9WRAM module and modify the value of WTOR_WRAM_LINK.
    This is done by either testing the external EYU9WRAM module or
    taking the setting from the WLM MOEB as set by EYU0WINT.
    
    EYU0WMAM has had the code that used to update WTOR_WRAM_LINK
    status based on the EMSTATUS record removed.
    
    The EMSTATUS field MASTYPE still has the
    EMSTATUS_MASTYPE_CPSMWRAM status bit set, or not set, in case
    an external API is interested.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH51320

  • Reported component name

    CICS TS Z/OS V6

  • Reported component ID

    5655YA100

  • Reported release

    40M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-12-06

  • Closed date

    2023-02-27

  • Last modified date

    2023-03-01

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

    PH51170

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

    UI90736

Modules/Macros

  • CJH0NLHD CJH0WNHD CJI0NLHD CJI0WNHD CJJ0NLHD CJJ0WNHD EYU0NLHD
    EYU0WMAM EYU0WNHD
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R40M PSY UI90736

       UP23/03/01 P F302

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 March 2023