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?

book

Article ID: 199263

calendar_today

Updated On:

Products

Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - SQL Performance Suite Detector for DB2 for z/OS Insight Performance Monitor for DB2 UDB for z/OS

Issue/Introduction

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.

Environment

Release : 19.0

Component : CA Detector for DB2 for z/OS

Resolution

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.