IBM Support

IT24819: MESSAGES NOT READ FROM Z/OS MQ INPUT QUEUE BY FLOW ON NON-Z/OS PLATFORM

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

  • A message flow deployed on a distributed operating system with
    an MQInput node configured to make a client connection to a
    Queue Manager on z/OS will fail to read any messages unless the
    index type of the queue is changed to GROUPID.
    
    One or both if the following errors might be written to the
    system log:
    
    BIP2680E: Failed to setup a MQ control callback for component
    'nodeName' to queue 'queueName' on
    queue manager 'qmgrName': MQCC=2; MQRC=2446
    (MQRC_NO_CALLBACKS_ACTIVE).
    
    BIP2680E: Failed to setup a MQ control callback for component
    'nodeName' to queue 'queueName' on
    queue manager 'qmgrName': MQCC=2; MQRC=2534
    (MQRC_OPERATION_NOT_ALLOWED).
    
    In addition, a service trace will show that the initial message
    retrieval fails with MQRC=2394 (MQRC_Q_INDEX_TYPE_ERROR).
    
    If the queue index is changed to GROUPID as a workaround,
    similar problems of not being able to read from the input queue
    might occur when trying to reprocess previously backed out
    messages that now have a group identifier set in the MQMD (as a
    result of APAR IT20272).
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10 and IBM App Connect
    Enteprise v11 running on a non z/OS platform but retrieving
    messages from a remote z/OS MQ Queue Manager.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A message flow deployed on a distributed operating system with
    an MQInput node configured to make a client connection to a
    remote Queue Manager on z/OS will fail to read any messages
    unless the index type of the queue is changed to GROUPID.
    
    One or both if the following errors might be written to the
    system log:
    
    BIP2680E: Failed to setup a MQ control callback for component
    'nodeName' to queue 'queueName' on
    queue manager 'qmgrName': MQCC=2; MQRC=2446
    (MQRC_NO_CALLBACKS_ACTIVE).
    
    BIP2680E: Failed to setup a MQ control callback for component
    'nodeName' to queue 'queueName' on queue manager 'qmgrName':
    MQCC=2; MQRC=2534 (MQRC_OPERATION_NOT_ALLOWED).
    
    In addition, a service trace will show that the initial message
    retrieval fails with MQRC=2394 (MQRC_Q_INDEX_TYPE_ERROR).
    
    If the queue index is changed to GROUPID as a workaround,
    similar problems of not being able to read from the input queue
    might occur when trying to reprocess previously backed out
    messages that now have a group identifier set in the MQMD (as a
    result of APAR IT20272).
    

Problem conclusion

  • The product now checks the platform that the Queue Manager is
    running on to set the appropriate MQGET options.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.15
    v11.0      11.0.0.3
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT24819

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-23

  • Closed date

    2019-02-04

  • Last modified date

    2019-02-04

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 February 2019