IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Future consideration
Workspace z/TPF Product Family
Categories z/TPF
Created by Guest
Created on Dec 16, 2021

RELATED IDEAS

z/TPF zMQ support for multiple MQ Connection Names to Multi-Instance (MI) MQ Servers

1. Z/TPF currently generally needs to interact with Multi-Instance (MI) distributed MQ Clusters through a Virtual IP Address (VIP) and Load Balancer or similar abstracting infrastructure.
2. This is because z/TPF does not support multiple MQ Connection Names within the MQ Definition File to the nodes in a Multi-Instance (MI) distributed MQ Server.
3. MI MQ Servers are composed of 2 nodes an Active node and a Passive node, that provide a High Availability (HA) implementation.
a. When the Active fails the Passive takes over the workload.
4. When MQ Connections are made to a MI MQ Server Cluster's active and passive nodes they ideally would use the same MQ Connection Name to both nodes.
5. Z/TPF zMQClients needs to be able to connect to both the Active and Passive MI MQ Nodes.
a. This so that when the Active Node fails over to the Passive, the zMQClient automatically begins interacting with the Passive Node that has been promoted to Active.
6. Z/TPF zMQServer Sender and Receiver Server Channels need to be able to connect to both the MI Active and Passive Nodes.
a. This so that when the Active Node fails over to the Passive, the zMQServer' s Sender and Receiver Family of Channels automatically begin passing traffic to the Passive Node that has been promoted to Active.
7. Problem Statement: Currently the z/TPF Client API and MQ Server Configuration only allow for one node when connecting to the non-z/TPF distributed Multi-Instance MQ Cluster.
8. Request for Enhancement (RFE):
a. z/TPF Client API and MQ Server Configuration need to be able to support interacting with non-z/TPF distributed Multi-Instance MQ Clusters.
b. When the MI Node switches to the Passive Node from the Active Node z/TPF MQ traffic needs to seamlessly flow to the now active Passive Node.

Idea priority Medium

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.