IBM Support

PK17361: EYUPN0005W AND EYUPN0011W MESSAGES HAVE INCORRECT TIME STAMPS FOR SAM EVENT SAMMAX AND SAMSTL.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Your CMAS EYULOG messages EYUPN0005W and EYUPN0011Whave
    incorrect time stamps for SAM events SAMMAX and SAMSTL.
    You will see the incorrect time stamp in the message in the
    user text area "Text=" . For example :
    11/23/2005 11:29:47 EYUPN0005W CMAS1 Notify created for SAM
          Context=PLXP0000, Target=CICS3, Sev=HS, Event=!!SAMMAX,
    11/23/2005 11:29:47 EYUPN0005W CMAS1 Text=MAXTASK at 13:55:52
    11/23/2005 11:30:02 EYUPN0011W CMAS1 Notify resolved for SAM,
          Context=PLXP0000, Target=CICS3, Sev=HS, Event=!!SAMMAX,
    11/23/2005 11:30:02 EYUPN0011W CMAS1 Text=MAXTASK at 13:56:07
    
    Program EYU0NLHD uses macro EYUQXXTZ to adjust the STCK for
    time zone offset and leap second adjustment. The adjustment
    values are in the literal pool and are based off of base
    register R2. However, EYUQXXTX uses R2 to access the CVTEXT2.
    When adding or subtracting from the STCK, instead of using the
    value in the literal pool, garbage is picked up instead.
    Additional Symptom(s) and Keyword(s): 5697E9301 300 MAX TASK
    STALL
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex/SM V3R1M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The timestamp contained in the text     *
    *                      portion of the EYUPN0005W or EYUPN0011W *
    *                      messages or the EVENT resource table    *
    *                      description field (EVENT_DESC) may be   *
    *                      incorrect for RTA SAM events issued for *
    *                      MAXTASK (!!SAMMAX) or STALL (!!SAMSTL). *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all MASes must be restarted.  Note     *
    *                 that the restarts do not need to occur at    *
    *                 the same time.                               *
    ****************************************************************
    When a MAXTASK or STALL event is detected in a MAS, method
    EYU0NLHD (NLHD) running in the MAS sets the time value that is
    used for the EYUPN0005W or EYUPN0011W messages and the EVENT
    resource table description field (EVENT_DESC).  NLHD uses
    internal macro EYUQXXTZ to normalize the time to the MAS's time
    zone.  During the normalization process, EYUQXXTZ may address
    literal values in NLHD.  However, these values are addressed by
    a base register that is overlaid when used as a work register
    by EYUQXXTZ.  This will result in the invalid timestamps seen.
    

Problem conclusion

  • NLHD has been updated to specify a non-base register for the
    work register used by EYUQXXTZ.  Additionally, EYUQXXTZ has been
    updated to not rely on literal values in the programs where it
    is invoked.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

  • The timestamp contained in the text
    portion of the EYUPN0005W or EYUPN0011W
    messages or the EVENT resource table
    description field (EVENT_DESC) may be
    incorrect for RTA SAM events issued for
    MAXTASK (!!SAMMAX) or STALL (!!SAMSTL).
    
    
    When a MAXTASK or STALL event is detected in a MAS, method
    EYU0NLHD (NLHD) running in the MAS sets the time value that is
    used for the EYUPN0005W or EYUPN0011W messages and the EVENT
    resource table description field (EVENT_DESC).  NLHD uses
    internal macro EYUQXXTZ to normalize the time to the MAS's time
    zone.  During the normalization process, EYUQXXTZ may address
    literal values in NLHD.  However, these values are addressed by
    a base register that is overlaid when used as a work register
    by EYUQXXTZ.  This will result in the invalid timestamps seen.
    
    
    NLHD has been updated to specify a non-base register for the
    work register used by EYUQXXTZ.  Additionally, EYUQXXTZ has been
    updated to not rely on literal values in the programs where it
    is invoked.
    

APAR Information

  • APAR number

    PK17361

  • Reported component name

    CPSM CICS 3.1

  • Reported component ID

    5655M1501

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-01-04

  • Closed date

    2006-02-03

  • Last modified date

    2006-03-02

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

    PK17342

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

    UK11387

Modules/Macros

  •    EYUQXXTZ EYU0NLHD
    

Fix information

  • Fixed component name

    CPSM CICS 3.1

  • Fixed component ID

    5655M1501

Applicable component levels

  • R100 PSY UK11387

       UP06/02/07 P F602

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.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
22 February 2023