IBM Support

IT29139: PCF response messages are written to the dead letter queue when .NET application uses PCF commands.

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

  • <p><span style="font-size:14px">Customers who are using a PCF
    Message Agent in their .NET application to send and receive PCF
    message occasionally see PCF Response messages being written to
    the dead letter queue (DLQ) instead of being returned to their
    application. </span></p><p><span style="font-size:14px">No
    exceptions or error codes are returned to the application when
    this occurs. </span></p><p> </p><p><span
    style="font-size:14px">The messages in DLQ have reason= 2052
    (MQRC_Q_DELETED).         </span></p><p><span
    style="font-size:14px">The temporary queue was closed/deleted by
    the application before all PCF response messages are
    received.</span></p><p> </p>
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of managed .Net applications which make PCF calls that may
    return multiple responses.
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A single PCF request message can generate multiple PCF response
    messages. The PCFAgent can be used to send a PCF request message
    and designed to wait for all the PCF responses to be received
    before returning them to the application.
    In some rare cases the PCF response messages were received by
    the PCFAgent in the wrong order which led to the send method
    returning prematurely and subsequently resulted in a number of
    the PCF response messages being written to the dead letter queue
    instead of being returned to the application.
    

Problem conclusion

  • The IBM MQ managed code has been corrected to handle the
    response correctly.
    
    After installing the fix of the APAR, to ensure all the response
    is received by the application then set the environment
    variable:
    MQ_ENABLE_STRICT_PCF_RESPONSE_CHECKING
    to any value in the environment used to execute the .NET
    application.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.10
    v9.1 CD    TBC.
    v9.1 LTS   9.1.0.5
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    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 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29139

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-15

  • Closed date

    2020-03-27

  • Last modified date

    2020-03-30

  • 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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 March 2020