PI05195: AN IMS MESSAGE PROCESSING REGION (MPR) IS INCORRECTLY TERMINATEDWHEN AN ABENDU3048 IS ISSUED FOR AN ESAF SYNC PHASE ONE FAILURE.

Obtain the fix for this APAR.

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.
  Keywords: DB2V10TGT/K
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IMS V13 customers using the IMS External     *
  *                 Subsystem Attach Facility ( ESAF ).          *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABENDU3048 STEP abends MPP regions      *
  *                      if an External Subsystem Phase1 Commit  *
  *                      request returns with RC=x'10'.          *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  IMS 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 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 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: subcode101 u0757 0757 757
  
  *** 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,
  in the table for function code x'0294', 'ABENDU3048' should be
  replaced with '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.
                                                   ||||||||||
                                                   ABENDU3055
  
  
  Also, under the U3055 abend, the following should replace the
  explanation and Analysis sections:
  
  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 is sysrouted FROM one or more of the following:

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

  PI05199 UI17864

Modules/Macros

• DFSESP10 DFSFESP0
  

Fix information

• Fixed component name

  IMS V13

• Fixed component ID

  5635A0400

Applicable component levels

• R300 PSY UI17864

     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.