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.