IBM Support

PM67099: WMQ: CSQ2005I FEEDBACK=331 DUE TO A SEQUENCE NUMBER MISMATCH FOLLOWING A DFS3494E TIMEOUT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CSQ2005I CSQ2QCP1 ERROR PROCESSING MESSAGE, FEEDBACK=331,
    XCFGNAME=<gname> XCFMNAME=<mname> TPIPE=<tpipename>
    .
    Feedback 331 corresponds to OTMA 31 x'1F':
           Explanation
           IMS  rejected the message, because the recoverable
           sequence number in the message-control information
           section of the message prefix does not match the IMS
           sequence number for the synchronized transaction pipe.
           If IMS receives 001F from a client, IMS stops the tpipe.
    .
    This is after:
    DFS3494E OTMA HAS TIMED OUT FOR TMEMBER/TPIPE xxxx/yyyy AND
    MOVED THE OUTPUT TO DFS$$TOQ.
    .
    The trigger for the out-of-sync sequence numbers is a CM0
    ACK timeout. The problem could happen for synchronous
    (MQ - IMS - MQ) as well as asynchronous (DRU) output for CM0
    messages with IMS V11.  IMS V10 will wait forever for the ACK.
    .
    This APAR will not fix the cause of the DFS3494E but will
    prevent the subsequent sequence error. IMS APAR PM67095 will
    be required to complete the fix.
    

Local fix

  • To recover from the problem, issue the MQ command
     /cpf RESET TPIPE<tpipe-name> XCFMNAME<member-name>
    where "cpf" is the command prefix for the queue manager
    subsystem
    or recycle OTMA using
     /STOP OTMA
     /STA OTMA
    .
    You can prevent the timeout from occurring by issuing
     /STA TMEMBER xxxxxxxx TIMEOUT 0
    or resolving the cause of the timeout
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 0 Modification 1 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: After an IMS OTMA timeout when using    *
    *                      the MQ IMS Bridge, recoverable sequence *
    *                      number errors may occur, as indicated   *
    *                      by message CSQ2005I with FEEDBACK=331.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If there is a delay in the queue-manager with the processing of
    an MQ IMS Bridge commit mode 0 output message from IMS, IMS can
    time-out the message, as indicated by message DFS3494E. The
    message is then moved by IMS to the timeout queue and IMS may
    then send another message via the same TPIPE. This can cause the
    sequence numbers for the TPIPE to become out-of-sync between
    MQ and IMS. Subsequent messages sent by IMS via the TPIPE will
    be rejected by the queue-manager with NACK x'1F', and message
    CSQ2005I with FEEDBACK=331 is issued. When IMS receives the
    NACK x'1F', it discards the output message.
    
    As a result of this problem, IMS APAR PM67095 has changed OTMA
    so that when the time-out occurs the output message is put back
    on the TPIPE queue rather than the timeout queue. Also, the
    APAR has changed OTMA so that when the NACK x'1F' is received,
    the output message is only discarded if requested by MQ,
    otherwise the TPIPE will be stopped. The MQ IMS Bridge therefore
    needs to be changed to indicate in a NACK x'1F' whether the
    output message is to be discard by OTMA.
    
    Additional keywords:
    MSGCSQ2005I MSGDFS3494E
    

Problem conclusion

  • CSQ2QCP1 has been changed to detect whether an output message
    has been received before and if so to indicate to OTMA that the
    message should be discarded.
    
    The PTF for IMS APAR PM67095 needs to be applied for the above
    change to be effective.
    010Y
    100Y
    CSQ2QCP1
    CSQ2242M
    CSQ7CBY
    CSQ7CB2
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

  • &#215;**** PE13/04/02 FIX IN ERROR. SEE APAR PM81031  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PM67099

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    018

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-06-18

  • Closed date

    2012-12-07

  • Last modified date

    2013-04-10

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

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

    UK90144 UK90145

Modules/Macros

  • CSQ2QCP1 CSQ2242M CSQ7CBY  CSQ7CB2
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UK90144

       UP13/01/16 P F301 Ž

  • R100 PSY UK90145

       UP13/01/16 P F301 Ž

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
10 April 2013