About

MQGem Software is a small company dedicated to providing affordable IBM MQ services and utilities. The company name reflects that each tool/program created is a little gem. The company was founded in 2012 by Paul Clarke, a former member of the IBM MQ Development team, and provides:

  • Utilities
  • Consultancy
  • Education
  • Design reviews

This blog is going to provide small tutorials, step-by-step instructions, feature highlights (“Did you know you could do this?”) about our gems, and any other interesting posts we can think of!

Choose to read posts about the product you are interested in from the menu bar.

You can follow MQGem Software on our various social media channels as well as following our blog, or drop us an email.

EmailFacebookTwitterLinkedInYouTubeWordPress

10 thoughts on “About

  1. Hi Morag

    I tried to use amqsslc sample program on MQ but it’s failing with MQCONNX FAILED WITH mqrc 2393 ssl initialization error

    MQ version is 9
    Cipher spec used is TLS 1.2 AES 256 SHA 256

    JRE version : IBM : version 8

    Like

    • Hi Nishchal,

      The client AMQERR01.LOG will have an error message showing more detail about why the 2393 reason code was given. Please look in there and see what it shows.

      Cheers,
      Morag

      Like

      • Hi Morag

        I am using the mq client on the same machine where queue manager is hosted

        Exported the MQ server variable

        Error log says

        AMQ9641: Remote CipherSpec error for channel TEST.ASL

        Even the amqsputc fails with the same reason 2393

        The command I used is

        ./amqssslc -m TEST -c TEST.ASL -x ‘localhost(4540)’ -k “/var/mqm/qmgrs/TEST/ssl/key” -s TLS_RSA_WITH_AES_256_CBC_SHA256

        Like

        • If you read the Response text of that error message it says, “Review the error logs on the remote system to discover the problem with the CipherSpec.”

          So, what does the queue manager error log say?

          Like

  2. Hi Morag

    AMQ9641: Remote CipherSpec error for channel TEST.ASL is from /var/mqm/errors/AMQERROR1.log . Nothing logged in Queue Manager log

    I am using the MQ client on the same machine on which Queue Manager is hosted .

    Like

    • The error you showed from the client error log will certainly have a matching message in a queue manager error log somewhere. This suggests that your client channel did not connect to the TCP listener you intended it to. Therefore the error message we are looking for is in another queue manager error log somewhere else. Do you have other queue managers on the same hostname? Can you check their error logs too.

      Like

  3. Is there a tool that can look at channel events from CHLAUTH rules in WARN mode (or look at channel status info) and generate the channel auth commands to create rules for the channels/IP addresses in question? We want to legitimise access that is currently being used, before enforcing the backstop rule.

    Like

    • I’m not aware of any tool that will process the particular sequence you are looking for. However, you may have seen our recent announcement of a closed beta for a new product that will work with MQ Events. This product will allow you to catch ANY MQ event and process it in any number of ways. It has the MQSCX control language built in to allow you to write scripts to do literally anything you can think of. So for example, it could automatically construct and issue MQSC commands, or write them to a file to review before issuing, using the data in an event message, e.g. MQRC_CHANNEL_BLOCKED_WARNING in your case.

      If this product is of interest to you, let us know and we could get you on the beta.

      I may have a little play with writing the script in question, and drop you a line later with an example of the above!

      Like

The team at MQGem would love to hear what you think. Leave your comments here.

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.