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.  MQHRF2_r library

    Posted 08/04/23 02:37 PM

    Hello, i am trying to connect to mq,

    AMQ6174I: The dynamically loadable shared library '/var/mqm/exits64/MQHRF2_r'
    could not be loaded. The system returned error number '2' and error message 'No
    such file or directory'.

     

    EXPLANATION:
    This message applies to UNIX systems. The shared library
    '/var/mqm/exits64/MQHRF2_r' could not be loaded.


    ACTION:
    Check that the file exists, and is either fully qualified or is in the
    appropriate director, also check the file access permissions.

    This file really does not exists on the file system, is there a way to install it?



    ------------------------------
    Matheus Francisco
    ------------------------------


  • 2.  RE: MQHRF2_r library
    Best Answer

    Posted 08/04/23 03:52 PM

    Hello,

    The Format field of the message descriptor contains the name of the message format. Some formats are standard (MQString, ...), others are specific.
    If the format field contains the name of a standard program/dll/..., there's nothing special to do.
    If the format field contains the name of a specific program/dll/..., this program/dll/... is called when the message is received and must be located in the exit directory (/var/mqm/exits64/ for example).

    The MQRFH2 format is a fairly common format in the MQ world, but is not a system format. MQRFH2 stands for MQ Rules & Formating V2, a format used by MQSI /IB / ACE, and the message has a specific structure: 
    - MQ header
    - MQSI header
    - MQ payload
    When these products are installed, the MQSI dll is usually added to the exit directory, allowing the message to be consumed.

    Apparently, the message here is in MQRFH2 format, as it comes from an MQSI/IIB/ACE environment.
    If you don't have this software installed, the easiest thing to do is to ask the sender to send you a message in "pure" MQ format and not in MQSI format.



    ------------------------------
    Luc-Michel Demey
    DEMEY CONSULTING
    lmd@demey-consulting.fr
    #IBMChampion
    ------------------------------



  • 3.  RE: MQHRF2_r library

    Posted 08/10/23 01:45 AM

    Like all built-in MQ message formats, those with a value in the format field of MQH...., this message format SHOULD be handled by the queue manager without the need for a data conversion exit. The file being reported does not exist, and you should not create one either.

    The error message you see is coming about as a result of data conversion of this built-in MQ format failing and the code dropping through to try the default behaviour which is to look for a data conversion exit of the name of the string found in the MQMD.Format field.

    This of course, shouldn't happen. Can I ask, are there any preceding error messages reporting problems with data conversion, with some code pages being reported or some such?

    Cheers,
    Morag



    ------------------------------
    Morag Hughson
    MQ Technical Education Specialist
    MQGem Software Limited
    Website: https://www.mqgem.com
    ------------------------------



  • 4.  RE: MQHRF2_r library

    Posted 08/10/23 09:17 AM

    This error, but the original error stopped after we changed the CCSID from 1208 to 819.

    AMQ7310W: Report message could not be put on a reply-to queue.

    EXPLANATION:
    The attempt to put a report message on queue QL.xxxxx on
    queue manager QM.xxxxxxfailed with reason code 2035. The message will be
    put on the dead-letter queue.
    ACTION:
    Ensure that the reply-to queue is available and operational.

    we use Linux and the sender queue manager is running on Windows.

    Thanks for answering.



    ------------------------------
    Matheus Francisco
    ------------------------------

    Original Message


Related Content