IBM Support

PI05199: AFTER APAR PM70167/ PTF UK92105, AN IMS MPP REGION IS INVALIDLY TERMINATED AFTER AN ABENDU3048 DUE TO ESAF SYNCH PH1 FAILURE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an IMS MPP region, which has utilized the IMS External
    Attach Facility (ESAF), initiates a syncpoint request, the
    external subsystem(s) that were accessed with the commit scope
    are called for Phase 1 (Commit Prepare) first followed by
    Phase 2 (Commit) processing.
    If the external subsystem is in a state such that its unable
    to process the phase 1 request from IMS due to the necessary
    resource being unavailable, it may pass back a x'10 return code
    to IMS. In response to this, IMS will subsequently issue
    a step U3048 abend that will result in the IMS MPR being
    inappropriately terminated.
    While the ABENDU3048 is correctly issued, it should issued as a
    psuedo abend and NOT result in the termination of the IMS MPP
    region.
    This problem occurs after application of APAR PM70167 /
    PTF UK92105.
    
     Additional symptom:  An abendU0757 SC101 can result
    in DFSQBFM0 if the region suffering the U3048 abend
    is a BMP that has not yet done a GU to the message
    queue when the failure happens.
    Keywords: DB2V10TGT/K subcode101 u0757 0757 757
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IMS V12 customers using the IMS External     *
    *                 Subsystem Attach Facility ( ESAF ) and have  *
    *                 IMS Apar PM70167 / PTF UK92105 installed.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABENDU3048 STEP abends MPP regions      *
    *                      if an External Subsystem Phase1 Commit  *
    *                      request returns with RC=x'10' and APAR  *
    *                      PM70167 / PTF UK92105 installed         *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    PM70167 attempts to correct problems in which IMS MPP regions,
    using the ESAF interface, make updates in Remote DB2 Subsystems,
    then fail on subsequent Phase 1 Commit processing requests with
    RC=x'10'. This is most commonly seen when the RACF ID of the
    USER requesting the update has been revoked on the Remote DB2.
    
    During a DB2 Phase1 Commit request, RC=x'10' is returned by
    DB2 APAR PM82151 when encountering the unique situation
    described above. IMS APAR PM70167 detects RCx'10' and issues
    STEP ABENDU3048.
    
    Problems associated with this approach include:
    1. The MPP region is STEP Abended and must be restarted.
    2. After a message driven BMP region encounters an ABENDU3048,
       the IMS Control region receives AbendU0757 SC101, in module
       DFSQBFM0, while attempting to enqueue an input msg to the
       SUSPQ when no input message exists.
    3. ABENDU3055 is more appropriate than U3048, and will be issued
       uniformly for all ESS Phase1 Commit requesters.
    
    Additional Keywords: U0757 U0757-101 U757 101
                         RC101 U0757-RC101
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    When RC=x'10' is returned from an External Subsystem Phase1
    Commit request, ABENDU3055 will now be issued. This Pseudo
    Abend will be processed as follows:
    
    1. Stop the Transaction
    2. Stop the Program
    3. Discard the input message
    4. Abend the program U3055 (Non Step Abend)
    
    Users desiring an alternate message disposition may use the
    Non-Discardable Message User Exit, DFSNDMX0, to suit their
    needs.
    
    The ABENDU0757 SC101 problem, in which an attempt was being made
    to requeue messages that had never been gotten by a message
    driven BMP, has been eliminated since this scenario no longer
    attempts requeuing to the Suspend Queue.
    
    
    In the IMS MESSAGES AND CODES MANUAL, under the section:
    Category B - conditions detected by external subsystem exits,
    'ABENDU3048' should be 'ABENDU3055'.
    
    X'0294'     EXTERNAL SUBSYSTEM COMMIT PREPARE. DETECTING MODULE:
                EXTERNAL SUBSYSTEM COMMIT PREPARE EXIT.
              x'10'   CommitPrepare was unsuccessful. The external
                      subsystem was unable to complete the request
                      because of the unavailability of a resource.
                      IMS terminates the application ABENDU3048.
                                                     ||||||||||
                                    Replace with-->  ABENDU3055
    
    
    Also, under the U3055 description, replace the Explanation and
    Analysis with the following:
    
    Explanation:
    The external subsystem (DB2t for z/OSt) was unable to complete a
    phase 1 commit request, and passed back return code 4 during
    normal application termination.  It can also occur when the
    phase 1 commit request passes back return code x'10' while in
    either a commit request during normal application termination or
    a non terminating commit request, such as during a Message Get
    Unique request.
    
    These return codes (RC04, RC=x'10') from DB2 indicates that a
    DB2 module has voted no to the commit request.
    
    Analysis:
    This is a pseudoabend issued by modules:
          DFSPCC20  When RC04 or RCx'10' is received for a normally
                    terminating application during phase 1 commit.
          DFSCPY00  When RCx'10' is received during phase 1 commit
                    for a non terminating scenario.
    
         The return code is passed back from DB2 to DFSESP10, which
         in turn passes the return code back to DFSFESP0. DFSFESP0
         sets up the pseudoabend.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI05199

  • Reported component name

    IMS V12

  • Reported component ID

    5635A0300

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-10-30

  • Closed date

    2014-05-09

  • Last modified date

    2015-02-23

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

    PI05195

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

    PI05201 UI17865

Modules/Macros

  • DFSESP10 DFSFESP0
    

Publications Referenced
GC18971506    

Fix information

  • Fixed component name

    IMS V12

  • Fixed component ID

    5635A0300

Applicable component levels

  • R200 PSY UI17865

       UP14/05/22 P F405 {

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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020