ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Why did Detector not Capture a -904 DISTSERV error that occurred in relation to a -254 error?
Article ID: 199263
Bind Analyzer for DB2 for z/OSSQL-Ease for DB2 for z/OSSYSVIEW Performance Management Option for DB2 for z/OSPlan Analyzer for DB2 for z/OSSubsystem Analyzer for DB2 for z/OSDatabase Management for DB2 for z/OS - Performance SuiteDatabase Management for DB2 for z/OS - SQL Performance SuiteDetector for DB2 for z/OSInsight Performance Monitor for DB2 UDB for z/OS
A -904 error was captured in detector on one subsystem. However, on a different subsystem it was not captured, but a -254 error was captured.
Release : 19.0
Component : CA Detector for DB2 for z/OS
Detector tracks SQL calls and picks up SQL Error from the DB2 control block provide the Thread was established. If the Thread did not get far enough where Detector was able to intercept the SQL Call, then we will not be able to track the SQL error.