IDB2 Thread History Overview Abnormal Ends filter not working well

Products

• SYSVIEW Performance Management Option for DB2 for z/OS
• Database Management for DB2 for z/OS - Administration Suite
• Database Management for DB2 for z/OS - Performance Suite
• Database Management for DB2 for z/OS - Recovery Suite
• Database Management for DB2 for z/OS - SQL Performance Suite
• Database Management for DB2 for z/OS - Utilities Suite
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS

Issue/Introduction

For a thread which failed with MAXTEMPS has Commits=1 Aborts=0 as follows in Sysview for Db2 for z/OS (IDB2) thread history.
Aborts should be non-zero since it failed. Thread is seen in Detector for Db2 for z/OS (PDT) as failed with SQL-904.

Even if there are threads which failed with workfile full condition and maxtemps, do not see them in thread history if filtered with “ Abnormal Ends  . .       y” .

Menu  Print  Tools  Help    SYSVIEW for DB2     SSID CAXX     08/30/24 17:58:14
                                 20.0.13         ssidPR20               USERID
    1 Overview  2 Exceptions  3 Resp Time  4 Locks  5 Buffers  6 More...
 
 R/HTDETL        Thread History Overview                                Row 1/28
 
 Plan    RBPAxxx   Corr ID CPSDDL          Connect DB2CALL    Auth ID xxxxxxx
 Date    08/30/24   Started 16:23:24.8718   RecType            ThdType ALLIED-N
 Term Cd NORMAL     Ended   16:23:26.8929   Commits 1 <====> Aborts 0  Excptns 2
 -------------------------------------------------------------------------------
 Times         in HH:MM:SS.T  Lock info         SQL info       Buffer pool info
 Elapsed Time App        2.0  Max Pg Locks   0  Select         Getpage         0
 Elapsed Time DB2        0.0  Lock Suspnds   0  Fetch          Read I/O        0
 Total DB2 CPU           0.0  Deadlocks      0  I/U/D       0  Read Eff      0.0
  DB2 CP Time            0.0  Escalations    0  Dynamic        Pref Reqs       0
  DB2 zIIP Time          0.0  Timeouts       0  DDL/DCL     0  Buf Updts       0
 Routine Elapsed         0.0                    Calls          BP Warn         0
 Wt All DB2 I/O          0.0  Other info        CallFail    0  Avg I/O    0.0000
 Wt All Lock/Ltch        0.0  Log Write      0
 Wt Log                  0.0  WLM Nam ........  Eligible times HH:MM:SS.T  % Tot
 Wt DB2 Services         0.0  L Prf No Stg      zIIP not used         0.0    0.0
 Wt DB2 Accel            0.0  Parallel Err   0  Accel Elapsed         0.0    0.0
 Wt Class3 Others        0.0  Parallel Task  0  Accel CP              0.0    0.0
 Other DB2 Time          0.0  Package Count  0  Accel zIIP            0.0    0.0
 
 Identification
   End User User ID    : XXXXXXX
   End User Workstation: YYYYYYY
   End User Transaction: ZZZZZZ
   Job Step Name       : BP
   Extended Corr Token : ZZZZZZ
   Product ID          : DSN12015
   Client Platform     : SSIDPTIB
   Accounting String   : 123456789

Resolution

The Termination Code(TERM CD) for the thread in question is NORMAL. The SMF record was cut with TERM CD=NORMAL even thought it failed with -904 due to
workfile full and maxtemps. After checking with IBM, it looks like it is the decision of calling application decision either to abort/abend or commit the UOW.
It appears that Db2 does not have any involvement on this decision. This is working as designed. Need to be little more careful in looking at threads failed with -904
either with workfile full or maxtemps.