Integration


This is an IBM Automation portal for Integration products. 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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.


Add a new idea Subscribe
Status Not under consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Apr 3, 2023

RELATED IDEAS

Binding IPs on multiple stacks dynamically

RECEIVING ON TCP

Starting listeners

 From the MQ manual: Receiving on TCP - IBM Documentation

 By default:

The TCP Listener program uses port 1414 and listens on all addresses available to your TCP stack.

TCP/IP listeners can bind only to addresses associated with the TCP/IP stack named in the TCPNAME queue manager attribute.

To start listeners for other addresses, or all available TCP stacks, set your TCPSTACK queue manager attribute to 'MULTIPLE'.

 When setting TCPSTACK to MULTIPLE, MQ are unable to bind dynamically  IPs in different TCP stack named in TCPNAME. MQ just bind the first address available in the TCPNAME. Then, it is necessary to define the IPs through VIPA DEFINE for the listeners start them with success.

I suggest enhancement for MQ to improve the way MQ binds the address to allow it binds in multiple stacks dynamically without being necessary to define the IPs previously, like other products.

 

  

 

 

 

Idea priority Low
  • Admin
    Matthew Leming
    Reply
    |     Aug 30, 2023

    This seems like a valid enhancement to the product. However, given that this situation can be made to work with appropriate VIPA configuration we don't see it as high priority and so we will be declining this idea. While declined the idea can still be voted, and commented, upon.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.