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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
In my case I want to change the Machine Hostname
OS: LINUX SLES15
Since using AWS Instances, the hostname is based on the IP. So, if I change the hostname "hostnamectl set-hostname CustomHostname" the MQ is not available...
How can I make it work with a new hostname?
Thank you
Ok, so not only would the mqm id need to set this MQS_IPC_HOST environment variable, but so would any other potential id on the server that would need to interact with IBM MQ. I don't consider this a tenable solution. At the current time, the MQ admin has to do things like delay the start up of the queue manager at reboot time to hopefully avoid this queue manager stability issue of the hostname being changed when the queue manager is running.
MQS_IPC_HOST has to be available to any command that is trying to do a local inspection or connection. I just tried it on a 9.3 qmgr and it all works fine - dspmq from a window that doesn't have the env var set gets "status not available" while doing it from the terminal where it was set before starting the qmgr, I can see the status
It is possible that I misunderstood the purpose of the MQS_IPC_HOST suggestion, but it did not correct the reported hostname issue when I tested it out in my IBM MQ sandbox. I did the following on a RHEL7 server running IBM MQ 9.2.0.4:
1) export MQS_IPC_HOST=server1
2) start queue manager
3) under root, change hostname to server1a with "hostname server1a"
After doing the above 3 steps, I was expecting the queue manager stability to not happen. However, I saw the same behavior of dspmq not working properly (returning Status Not Available), local connections to the queue manager no longer working (amqsput getting 2059 errors), etc. So I don't believe MQS_IPC_HOST is a viable workaround for this issue.
Thank you for the suggestion, as I was not aware of that. Because having an admin manage the setting of an environment variable before the queue manager starts is not ideal, I would still recommend that this idea is considered open and IBM MQ adjusts the queue manager start up code to programmatically set this MQS_IPC_HOST environment variable if it is unset to something unique (perhaps to the system hostname). It sounds like this should resolve the reported issue of a system hostname change, with also not requiring any manual interaction from the IBM MQ admin.
The MQS_IPC_HOST environment variable already gives a way to "fix" the hostname used by MQ regardless of the real hostname. See
https://www.ibm.com/docs/en/ibm-mq/9.2?topic=reference-environment-variables