IDB2 External IQL based exception not being tripped when Db2 hung processing any request
Article ID: 245475
Updated On: 08-12-2022
Products
Issue/Introduction
Why is the Application exception functioning well but not IQL exception when both uses the same IFCID 148 data? Please clarify in detail.
Environment
Release : 20.0
Component : SYSVIEW Performance Management Option for DB2 for z/OS
Resolution
The difference between IQL exceptions and the standard IQL exceptions is in the way IDB2 acquires the data. The IQL exceptions depend on DB2 to provide the product with the IFCID records which the product processes and filters as a standard IQL request. After that IDB2 sends the output of an IQL exception report to the exception system which performs some actions that is set up for this particular exception. If DB2 hung processing some request and does not gives IDB2 the IFCID records that were requested -no data will be available to display- No data will be seen there. The standard exceptions work in an absolutely different way. The vast majority of them will be looking into the DB2 address spaces to harvest the data from DB2 control blocks directly. So IDB2 is able to harvest data even from a hanging DB2 subsystem as long as the respective address spaces are still alive. In short, the standard application exceptions do not use IFCID 148 data and instead get the data from DB2 control blocks directly.
Feedback
