MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Mon March 17, 2025 03:46 PM

    Hello,

    Can you please tell me pros and cons of connecting JMS client directly to queue manager on RHEL or queue manager on Z/OS which one is preferable.

    I have setup where JMS client connects to queue manager on RHEL and then pass messages to queue manager on Z/OS. What is reason of introducing an extra layer.

    Directly MQ client connects to Queue manager on Z/OS, is it possible?

    Thanks in advance.

    KP



    ------------------------------
    K Priyanka
    ------------------------------


  • 2.  RE: JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Tue March 18, 2025 01:46 AM

    Did you think to check the financial side of things?

    Running a lot of SVRCONN instances on zOS can be quite expensive. It may be cheaper to use a distributed qmgr as concentrator...



    ------------------------------
    Francois Brandelik
    ------------------------------

    Original Message


  • 3.  RE: JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Tue March 18, 2025 04:50 AM

    Hi KP,

    Direct connection is certainly possible. Take a look at Using client concentrators with MQ for z/OS  for comparison of direct connections with client concentrators. We see both used.

    In scenarios where your RHEL queue manager is in the cloud and your z/OS queue manager is on-prem we would definitely recommend going via the RHEL queue manager. See IBM MQ cloud architecture blueprint see slide 14.

    Feel free to reach out if you have further questions.

    Regards, Matt.



    ------------------------------
    Matt Leming
    STSM, IBM MQ for z/OS
    Email: lemingma@uk.ibm.com
    ------------------------------

    Original Message


  • 4.  RE: JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Wed April 09, 2025 10:01 AM

    Thank you so much!

    My app is in cloud and RHEL queue manager is on on prem along with z/OS queue manager.

    APP(in AWS) -> RHEL->Z/os

    if you can provide your input for above mq connectivity. what all points I should consider, like pros and cons.

    With Regards

    KP



    ------------------------------
    Kumari Priyanka
    ------------------------------

    Original Message


  • 5.  RE: JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Tue March 18, 2025 01:48 PM
    Client applications connecting directly to z/OS queue managers works well, but the CHIN address space takes a CPU hit for each connect/disconnect, etc.  Connect and disconnect are the two most expensive MQ API requests from a CPU perspective, opening and closing a temporary dynamic queue are the next most expensive, opening and closing a permanent queue are the next.   So if the client applications are well behaved, that tends to connect once and do a lot of work using the same queues before disconnecting - those work quite well.  Client applications that connect/open/put or get/ close/ disconnect are not good candidates to connect directly to a z/OS queue manager. The General Purpose CPU costs (MIPS) can be driven up very quickly with badly behaved clients.  

    Hope this helps




    Original Message


  • 6.  RE: JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Wed March 19, 2025 09:27 AM
    Edited by bruce2359 Sat March 22, 2025 07:18 PM

    This is an odd thread in that everything we do in IT on any computer platform drives up CPU utilization.  The z/OS CHIN is no different.  Examining only CHIN CPU utilization and its cost misses the CHINs value to successfully drive millions of concurrent transactions per second. 



    ------------------------------
    bruce2359
    Consultant/trainer
    CTTECH - Computer & Telecommunications Technology
    West Coast, almost
    000-000-0000
    ------------------------------

    Original Message


  • 7.  RE: JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Fri April 04, 2025 07:20 AM

    One additional issue has to be considered regarding non- and z/OS:

    Syncpoint considerations in IBM MQ applications

    In your IBM MQ application, you can specify on every put and get call whether you want the call to be under syncpoint control. To make a put operation operate under syncpoint control, use the MQPMO_SYNCPOINT value in the Options field of the MQPMO structure when you call MQPUT. For a get operation, use the MQGMO_SYNCPOINT value in the Options field of the MQGMO structure. If you do not explicitly choose an option, the default action depends on the platform:

    • [UNIX, Linux, Windows, IBM i]The syncpoint control default is NO.
    • [z/OS]The syncpoint control default is YES.

    This means that it is better when an application controls the syncpoint management by itself in the code because it would change when switching to another platform.



    ------------------------------
    Norbert Pfister
    system engineer
    Nuremberg
    Germany
    ------------------------------

    Original Message


  • 8.  RE: JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Fri April 04, 2025 07:55 AM

    Hi Norbert, 

    That is indeed a difference between the platforms when using the MQI. But it doesn't apply with JMS as that has its own set of behaviour as required by the JMS spec.

    Regards, Matt.



    ------------------------------
    Matt Leming
    STSM, IBM MQ for z/OS
    Email: lemingma@uk.ibm.com
    ------------------------------

    Original Message


  • 9.  RE: JMS client connectivity to queue manager on RHEL or Z/OS which is preferable

    Posted Fri April 04, 2025 09:10 AM

    KP asks:  "Can you please tell me pros and cons of connecting JMS client directly to queue manager on RHEL or queue manager on Z/OS which one is preferable."

    An application should connect to a qmgr where the needed resources (data and supporting software) reside.  

    KP asks: "I have setup where JMS client connects to queue manager on RHEL and then pass messages to queue manager on Z/OS. What is reason of introducing an extra layer."
    Historically, z/OS did centralized and massive batch processing - printing bills, updating data bases, and such. z/OS platform can also process millions of transactions per second.

    KP asks: "Directly MQ client connects to Queue manager on z/OS, is it possible"

    Yes. Possible and preferable for very large applications such as government, credit card and banking, where aggregate cost per transaction is low. 



    ------------------------------
    bruce2359
    Consultant/trainer
    CTTECH - Computer & Telecommunications Technology
    West Coast, almost
    000-000-0000
    ------------------------------

    Original Message


Related Content