Category: IBM-MQ

Applicaiton is connecting to IBM MQ QMGR with GCM cipher and after some time we see below error on the logs Above error is because

Although MQ was built for high transaction volumes, poor architecture and application design can compromise its ability to process messages as fast and effectively as

IBM MQ provides File transfer service using MQFT packages with in the MQ . This feature basically require Advance license . If you have Advance

Here in this post We attempt here to put a Checklist of problems and solutions for WebSphere MQ channel issues. In case of channel issues,

MQSeriesGSKit is required to enable SSL on IBM MQ QM1: (Path : C:\Program Files (x86)\IBM\WebSphere MQ\Qmgrs\QM1\ssl) 1.Creating key store runmqakm -keydb -create –db qm1key.kdb -pw

Here you will see the high level steps required to setup the multi instance qmgr for the quick reference Pre-requisites: Install MQ in both active

The reason ‘2085’ (‘MQRC_UNKNOWN_OBJECT_NAME’) occurs when An MQOPEN, MQPUT1 , or MQSUB call was issued, but the object identified by the ObjectName and ObjectQMgrName fields

log4j vulnerability is also called Log4Shell or LogJam. Here we will is the impact of this with IBM MQ distributed environment . Based on the

To find out which applications are connecting to a particular svrconn channel you can use the below command: dis chs(channel name)Note: Replace channel name with

The MQ sample “amqsblst” (also called “Blast”) will be used to test putting/getting alarge quantity of messages (10,000) into the queue. In Unix the following