IBM Support

PK46095: MULTIPLE EYUPN0007W MESSAGES PRODUCED FOR THE SAME EVENT NOTIFIC ATION.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You use the RTAACTV view to discard an active RTA analysis, and
    modify the EVALDEF, and install the RTADEF. You then repeat this
    same process. After installing the RTADEF twice, the analysis
    becomes true and produces three EYUPN0007W messages for the
    the same analysis. Only one EYUPN0007W message should be
    produced.
    Additional Symtoms and Keywords : 5655-M1501 R310 R300 Real Time
    Analysis CICSPLEX CPSM
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:    You have an RTADEF which is con-     *
    *                      trolled by a PERIODEF.  You discard     *
    *                      the active RTADEF from the RTAACTV      *
    *                      view, modify the EVALDEF, and re-       *
    *                      install the RTADEF.  When the evalu-    *
    *                      ation conditions are met, more than     *
    *                      one EVENT record appears.  If the       *
    *                      active RTADEF is deactivated or         *
    *                      discarded, or if monitored MASes        *
    *                      are brought down, all of the EVENTs     *
    *                      are not removed.                        *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be recycled to pick    *
    *                 up the new code.  Note that the restarts     *
    *                 do not need to be done at the same time.     *
    ****************************************************************
       When an RTADEF is installed under the control of a PERIODEF,
    an entry is added to a cache list whose key contains the RTADEF
    name and the PERIODEF name.  Before the install starts, a look-
    up is performed against the list, and if the element is found,
    the install fails with appropriate messages.  After the install
    completes successfully, a new element is added to the list, but
    the status is not checked to detect a duplicate entry.  When an
    RTADEF is installed under the control of a PERIODEF, the initial
    install may have to wait on outstanding resources.  If the time
    of day is within the active period, the install method is called
    to activate the definition.  Since the initial call is still not
    complete, the cache list lookup does not find an element, the
    activation completes, and an element is added to the installed
    definition list.  Meanwhile, the install which was waiting on
    resources resumes and completes.  There are now two instances of
    the installed RTADEF active, but only one instance appears in
    the RTAACTV view.  If the active definition is discarded or de-
    activated, the EVENT associated with the second instance will
    not be removed.
       Because the key to the Installed Definition list contains the
    PERIODEF name, if the RTADEF is installed a second time with a
    different PERIODEF, or with no PERIODEF, an additional entry
    will appear in the RTAACTV view, and will cause additional EVENT
    instances to appear, but the notification index list does not
    contain the PERIODEF name, so only one EVENT will be removed if
    the RTADEF(s) are discarded or deactivated.
    

Problem conclusion

  •    Module EYU0PMDI (PMDI - Install MRM Definition) was modified
    to add an element to the Installed RTADEF list at the beginning
    of the install process.  If the ADD fails, the installation is
    terminated.  If the installation fails after the element has
    been added, it will be removed.  Code was also added to detect
    an attempt to install the same RTADEF as both a timed and un-
    timed definition, and to fail the attempt with an appropriate
    message.  Module EYU0PGDI (PGDI - RTA Manual Install Driver) was
    modified to provide better detection and feedback for install
    failures, including duplicate installs.  Module EYU0PMAT (PMAT -
    MRM Timed Activate / Deactivate) and EYU0PMDD (PMDD - Discard
    RTAMRM Definition) were modified to better manage transition be-
    tween PERIODEFs with overlapping time ranges.  Several other
    modules were updated or reassembled to incorporate modifications
    to the RTAMRM SPEC Descriptor (PMSD) and the Installed RTADEF
    cache list element (PMRL).
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

  • ž**** PE07/07/26 FIX IN ERROR. SEE APAR PK49787  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PK46095

  • Reported component name

    CICSTS 3.X Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    50M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-05-30

  • Closed date

    2007-07-10

  • Last modified date

    2007-08-03

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

    PK44000

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

    UK26923

Modules/Macros

  •    EYURPMRL EYURPMSD EYU0DVRC EYU0PGDD EYU0PGDE
    EYU0PGDI EYU0PGRS EYU0PMAT EYU0PMCE EYU0PMCS EYU0PMDD EYU0PMDI
    EYU0PMMN EYU0PMTR
    

Fix information

  • Fixed component name

    CICSTS 3.X Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK26923

       UP07/07/12 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