If you're interested in the gory details of what goes on deep in the internals of an IBM MQ Cluster - help is available. Also there's now this blog/technote: https://t.co/S3FnTIhBvb
Before I look into the legal options, anyone @vueling like to comment on why they provide no contact information anywhere for customer service (only an awful 'bot' on the website) and auto-reject compensation for delayed flights without any good explanation?
Quick post (and sample code) showing how you can override a fixed Queue Manager name in 'legacy' client applications and enable use of many modern (CCDT based) IBM MQ features. https://t.co/oeOOIlMkVJ
@MQGem And if you are, don't forget my new favourite MQSC command DIS APSTATUS as another way to get insight on how connections are related to each other.
If the main thing missing from your day was my soothing tones giving you an update on scaling options in IBM MQ, boy do I have good news for you! https://t.co/6jKI0bASlK
Just updated https://t.co/Rp6lsiJepA with example code and scripts demonstrating how you can now rebalance request reply applications in an IBM MQ Uniform Cluster
@dalelane Sadly it really isn't. Infuriating controls ruined any hope of getting into the story for me. Might be marginally more bearable with a mouse.
And here's a deeper dive into how new IBM MQ 9.2.4 features can enable request reply applications to take advantage of Uniform Cluster balancing: https://t.co/jCjugO7jIM
@dalelane I never understood the argument that it solved the inbox problem. It only ever meant one of two things - people were using it for stuff that was less important (so you could mark thread/channel as read), or fewer people were using it to talk to you full stop.
@gouda_65 Hi @gouda_65 - all is not lost! This blog post effectively got tided up and inserted into the KnowledgeCenter as https://t.co/vYbz0djsTr - hope that has what you're looking for.