PK95741: DB2 THREAD STATUS "IN-ABORT" NOT DISPLAYED INSTEAD STATUS OF "IN-DB2" IS REPORTED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During Thread ROLLBACK either as a result of an application
  abend or because SQL ROLLBACK command is issued OMPE shows
  a status of IN-DB2 rather than IN-ABORT status.
  
  For example ZALLT screen will show
   THDA
  + *
  + Elapsed      Planname  CPU    Status       GetPg  Update
  + ----------   --------  -----  ------------ ------ ------
  + 01-22:18     KO2PLAN   00.0%  IN-DB2        42248  16714
  
  And yet
  
  The Sql-Count may reflect and abort has occurred on screen
  ZTSCNT (SQL Counts after zooming a thread)
  
  >                              CURRENT SQL COUNTS
   PLAN
  + Thread:  Plan=KO2PLAN   Connid=RRSAF    Corrid=
  + Attach:
  + Luwid=USCACO01.DB2D91B.C47C35EA94EF=28
   sqls
  + Commit         =    8379  Abort          =       1
  + Open Cursor    =    8376  Close Cursor   =    8376
  
  A partial list of screen where the status field follows
  VTAM or Classic Mode
  ZALLT ZALLU ZTDTL
  CUA Mode
  KD2OATCD KD2VTHD6 KD2OTSOD KD2OABACD KD2OUSAD KD2ODISD
  
  IN ABORT INCORROUT DB2 STATUS
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Classic Interface                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When threads doing a rollback SQL       *
  *                      command or rolling back because of an   *
  *                      ABEND, the status shows IN-DB2 instead  *
  *                      of IN-ABORT or IN-TERM-THRD.            *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  Further detailed status for threads rolling back was not being
  checked.
  
  PROBLEM CONCLUSION:
  Check for threads in IN-ABORT or IN-TERM-THRD status.
  

Problem conclusion

• Check for threads in IN-ABORT or IN-TERM-THRD status.
  

Temporary fix

Comments

APAR Information

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

  PK82904

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

  UK51187

Modules/Macros

• KO2CTHSA KO2CTHSS KO2CTHS2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R420 PSY UK51187

     UP09/10/21 P F910

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.