View Only
  • 1.  sequence of mq components

    Posted Thu September 28, 2023 09:54 AM


    I'm new to mq and need to know in what sequence we creates listener, channel and all queues. which one first then and in last to manage messaging using it.

    Please provide each step by step to create and configure.

    Amir Ali

  • 2.  RE: sequence of mq components

    Posted Thu September 28, 2023 10:10 AM


    pls check the IBM MQ tutorial link,


    veena ramachandran


  • 3.  RE: sequence of mq components

    IBM Champion
    Posted Thu September 28, 2023 04:23 PM
    Edited by Luc-Michel Demey Thu September 28, 2023 04:24 PM

    When you create MQ objects, either interactively or via a script, the order of creation is irrelevant.
    You can create a sender channel that references an xmitq before this xmitq, or an alias queue that references a local queue before the local queue.
    It doesn't really matter.
    What's important is that the xmitq exists when the channel starts, or that the local file exists when the alias file is used.
    The same goes for the listener.
    On the other hand, if you create AUTHRECs, the accounts or groups must exist at the time of creation.

    Luc-Michel Demey

  • 4.  RE: sequence of mq components

    Posted Fri September 29, 2023 08:20 AM

    Hello Amir:

    The following tutorial is very comprehensive, and includes workarounds for Test queue managers regarding channel authentication records.
    It provides the steps to allow a non-Administrator user (fulano) to use a server-connection channel and to put/get messages from a queue.
    Even though the focus is for Linux, the actual MQ steps are the same for Windows.
    Configuring an IBM MQ queue manager to use a dedicated Listener, Channel and Queue in Linux
    The chapters are:
    Chapter 1: User "root" adds the proper user and group in both hosts
      User "fulano" is not an MQ administrator, and will be allowed to put/get messages.
      User "bob" is not an MQ administrator, and will NOT be allowed to put/get messages.
    Chapter 2: MQ administrator (user "mqm") creates a queue manager with the basic/normal objects in host-1
    Chapter 3: MQ administrator adds the dedicated objects.
    Chapter 4: User "fulano" from host-2 puts and gets messages using the dedicated objects.
    Chapter 5: User "fulano" from host-2 uses runmqsc to look at CURDEPTH on MY.Q
    Chapter 6: User "bob" from host-2 fails to put/get messages using the dedicated objects
    The dedicated objects are:
    - Listener (such as MY.LISTENER in port 1420)
    - Server-Connection Channel (such as MY.CHANNEL)
    - Queue in Linux (such as MY.Q)
    - Channel Authentication Record (CHLAUTH) for this server-connection channel that allows only the user "fulano" who is a member of the group "mqusers".
    - Authority records for group "mqusers" to display, put, get, browse, etc. from the dedicated queue.

    I hope that this is helpful.

    Thank you for using IBM products!
    Angel Rivera, IBM MQ Support

    Angel Rivera
    IBM MQ Support
    Research Triangle Park NC