IBM Support

PM84711: OTMA MESSAGE RESCHEDULED INSTEAD OF DELETED AFTER U0243 ABEND ( MESSAGE EXPIRATION ). ONE SYMPTOM IS HUNG BE MESSAGE REGION.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • OTMA CM1 message is rescheduled instead of discarded after a
    U0243 abend.
    In customers's shared queue environment, this eventually caused
    a hang in a Back End message region due to double use of input
    YTIB on the Front End IMS. Due to the abend, DFS3688I is sent
    to FE, causing YTIB to run to deliver it; the rescheduled
    message eventually runs on the FE IMS which causes a YTIB
    serialization issue with YTIB_SYNC_PTR.
    The failing flow involves a PWFI region posted to process a
    message which expires before it is processed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V11 users of APPC/IMS timeout        *
    *                 (APPCIOT= in DFSDCxxx member) or OTMA        *
    *                 transaction expiration (EXPRTIME= parameter  *
    *                 on TRANSACT macro).                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: After an ABENDU0243 is encountered,     *
    *                      the input message may be incorrectly    *
    *                      requeued instead of discarded.          *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    When a scheduled message driven application program issues a
    message GU or CHKP call that subsequently results in an
    ABENDU0243 situation, the input message that is in progress
    may incorrectly get inappropriately requeued to its transaction
    when it should have been discarded.
    
    This problem can occur in the either of the following scenarios:
    
    1. a PWFI region, previously waiting on scheduling subqueue 6
       for new work, gets posted to process a newly available input
       message who's time limit expires prior to being processed.
    
    2. an applicaton message GU or CHKP call that results in IMS
       syncpoint procesing being initiated first to commit inflight
       work associated with the previous unit of recovery.
    
    
    In the reported error, the cause of the input message being
    wrongfully requeued is due to the fact that the ABENDU0243
    condition indictor, checked by module DFSFXC40 during ABTERM
    processing for determining input message handling, was
    erroneously being reset by module DFSFXC30 after the timeout
    condition was detected but prior to the U0243 abend being
    issued.
    
    It is important to make the distinction that the problem
    reported is not applicable to the case where an ABENDU243
    condition is suffered during IMS Scheduling prime GU processing.
    

Problem conclusion

  • GEN:
    KEYWORDS:
     SYSPLEXSQ
    
    *** END IMS KEYWORDS ***
    Code in module DFSFXC30 has been modified to preserve the
    DLREXPIR indicator setting so that it is available to DFSFXC40
    during subsequent ABENDU0243 ABTERM processing.
    
    This will ensure that the input message is correctly discarded.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM84711

  • Reported component name

    IMS V11

  • Reported component ID

    5635A0200

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-03-13

  • Closed date

    2013-07-10

  • Last modified date

    2013-08-02

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

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

    PM92008 UK95733

Modules/Macros

  • DFSFXC30
    

Fix information

  • Fixed component name

    IMS V11

  • Fixed component ID

    5635A0200

Applicable component levels

  • R100 PSY UK95733

       UP13/07/17 P F307 ¢

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":"100","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2013