IBM Support

IT17407: WHEN IBM MQ TOPICS HAVE DEFPSIST(YES) IIB MONITORING ARE STILL PUBLISHED AS NON PERSISTENT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • A defect exists such that monitoring messages are published with
    MQPER_NOT_PERSISTENT rather than MQPER_PERSISTENCE_AS_TOPIC_DEF.
    This means that all monitoring messages are always published as
    non persistent, irrespective of the IBM MQ definitions.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10.0 attempting to publish
    persistent monitoring events.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    IBM Integration Bus monitoring event messages are published as
    non persistent by default.
    
    The IBM MQ documentation details how to configure MQ topics and
    subscriptions so that publications can be published as
    persistent, for example:
    
    DEFINE TOPIC(IIBMONITORING.TOPIC)
      TOPICSTR('$SYS/Broker/<brokerName>/Monitoring/<egName>')
      DEFPSIST(YES)
    
    DEFINE SUB(IIBMONITORING.SUB)
      TOPICSTR('$SYS/Broker/<brokerName>/Monitoring/<egName>/#')
      DEST(<destqueue>)
      DESTQMGR(<destqmgrname>)
    
    Note: The wildcard '#' can be used in the subscription TOPICSTR
    but NOT in the topic TOPICSTR.
    
    However, even with these definitions in place, monitoring
    publications from the named <egName> are still published as non
    persistent.
    

Problem conclusion

  • Monitoring messages are now published with
    MQPER_PERSISTENCE_AS_TOPIC_DEF rather than MQPER_NOT_PERSISTENT
    by default. This means that if you choose to define the topics
    as persistent, the setting will be honoured.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.7
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT17407

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-18

  • Closed date

    2016-11-23

  • Last modified date

    2016-11-23

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

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

Fix information

  • Fixed component name

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020