Profile

Hi Mike, The error you are seeing:- AMQ9641: Remote CipherSpec error for channel 'CLOUD.APP.SVRCONN' to host tells me that you don't have the same CipherSpec configured at both ends of your CLOUD.APP.SVRCONN channel. One end of the channel is defined on your queue manager, as a CHANNEL object ...

This is part of a series of blog posts which will cover features of IBM MQ that I happen to be using this week. I spend a lot of time using MQ, and not everything counts as an MQ Little Gem , or a Quirk , but is still interesting to hear about. Read other posts in this series . In the new version ...

You can install MQ in its own unique directory by following the instructions here: https://www.ibm.com/docs/en/ibm-mq/9.4.x?topic=imlur-installing-additional-mq-installations-linux-using-rpm-command Then when you are ready at some point later, you can move your queue managers, individually, one at a ...

3070 is MQCACF_RESPONSE_Q_MGR_NAME. You'll get that parameter in every response from z/OS, just in case the command was issued using CMDSCOPE and the queue manager name isn't the one you are connected to. Cheers, Morag ------------------------------ Morag Hughson MQ Technical Education Specialist ...

Thanks - I'll let IBM know the correction that is needed. I suspect what has happened is that page was originally written before the DISCINT field was even applicable to SVRCONN channels, and it didn't get quite enough of an update to explain the different default values when the field was added to SVRCONN ...