IBM Support

IT43716: CHANNELS WERE NOT RUNNING BECAUSE THE CHANNEL INITIATOR PROCESS (RUNMQCHI) TERMINATED.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The Channel Initiator Process runmqchi reports error 2009
    (MQRC_CONNECTION_BROKEN) in the error log (AMQERR*.LOG) and
    terminates
    
    AMQERR01.LOG:
    
    XX/XX/XX XX:XX:XX - Process(8,358 $Z1YV 33554618.1) User(....)
    Program(runmqchi) Host(XXXXX)
    VRMF(X.X.X.X) QMgr(XXXXX)
    
    AMQ9510: Messages cannot be retrieved from a queue.
    
    EXPLANATION:
    The attempt to get messages from queue 'SYSTEM.CHANNEL.INITQ' on
    queue manager 'XXXXX' failed with reason code 2009.
    
    2.) The channel initiation queue might be full.
    
    3.) An agent dead error report by the Execution Controller.
    
    Extract from the FDC:
    
    | Probe Id          :- ZX005035
                 |
    | Component         :- zxcProcessChildren
                 |
    | Program Name      :- amqzxma0
                 |
    | Major Errorcode   :- zrcX_AGENT_DEAD
                 |
    | Probe Type        :- MSGAMQ5009
                 |
    | Probe Severity    :- 2
                 |
    | Probe Description :- AMQ5009: IBM MQ agent process 1360527723
    has           |
    |   terminated unexpectedly.
                 |
    | Arith1            :- 1360527723 (0x5118016b)
                 |
    

Local fix

  • The channel initiator process runmqchi can be started manually.
    

Problem summary

  • An agent did not handle a file system error in a correct way and
    terminated.
    The channel initiator process reported this error and stopped
    itself.
    

Problem conclusion

  • The mapping of file system errors to internal error codes was re
    The handling of some errors was improved according to implementa
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    Version    Maintenance Level
    v8.1       8.1.0.20
    The latest available maintenance can be obtained from
    'Recommended Fixes for IBM MQ'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    If the maintenance level is not yet available information on
    its planned availability can be found in 'IBM MQ planned
    maintenance release dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

  • The channel initiator process, runmqchi, should be manually
    restarted if it is not running.
    

Comments

APAR Information

  • APAR number

    IT43716

  • Reported component name

    MQ FOR HPE NS O

  • Reported component ID

    5724A3903

  • Reported release

    81X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-05-09

  • Closed date

    2024-03-18

  • Last modified date

    2024-03-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    MQ FOR HPE NS O

  • Fixed component ID

    5724A3903

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81X","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
19 March 2024