IDB2 dbgexrpt IQL is not reporting the exception definition name

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

Issue/Introduction

Trying to list our defined exception definitions using dbgexrpt and while the exception file name heading shows on the report, the actual data does not.  For example:

2023/08/10  10:49:27                                                                                                       PAGE    1
                                                   LIST OF EXCEPTION DEFINITIONS                                                    
                                                          TYPE: SUBSYSTEM                                                           
STATUS SSN  <----------------------------------------  EXCEPTION TEXT  ----------------------------------------> NAME               
------ ---- ---------------------------------------------------------------------------------------------------- --------           
ACTIVE **** IS&SSNS06&LVL # of EDM request failures - no pagesavailable: &VALUEXX                                                   

                                                                               
                   List of Subsystem Exception Definitions                     
                                                                    Row 505/507
Commands: ADD=Add exception, ACTALL/INACTALL=Activate/inactivate all exceptions
Actions: U=Update current and permanent, P=Update permanent definition only,   
         C=Copy, D=Delete, A=Activate, I=Inactivate, B=Browse.  Use F6 to add. 
STA/NAME SSN   <---------------  EXCEPTION TEXT  --------------->              
_ ACTIVE ****  IS&SSNS06&LVL # of EDM request failures - no pages              
SS000001       available: &VALUEXX                                             

Environment

Release : 20.0

Resolution

The problem was caused by the use of an old exception file. Using the new exception file resolved the problem.