Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Delivered
Workspace Db2 for z/OS
Created by Guest
Created on Apr 12, 2016

DB2 MQ Listener - Reconnect and resume processing after DB2/WLM outage

System: DB2 MQ Listener
Actor: Business User needing new feature

DB2 MQ Listener is used for integration of consumer/investment banking product offerings, improving customer experience.

Description: We encounter service interruptions with the Listener under two scenarios: 1) After a cycling of DB2 subsystem to which the listener connects, reconnection is not automatic - recycling of Listener is required; 2) After an outage of the WLM supporting the stored procedure(s) used by the Listener is mitigated, the Listener will not process its MQ queue until a *new* message arrives on the queue.
  • Admin
    Janet Figone
    Reply
    |
    Apr 24, 2019

    For case: After an outage of the WLM supporting the stored procedure(s) used by the Listener is mitigated, the Listener will not process its MQ queue until a *new* message arrives on the queue.

    Explanation: When the WLM is outage, the Listener continues get the MQ message and invoke the stored procedure. Listener tries that process for the message until it hit the backout thread-hold then the message is sent to the backout queue. When WLM is up, all the messages on the queue are processed as normal.

    To process the messages are sent to the backout queue. The user can have another listener to listen to the backout queue and invoke the stored procedure.