Why wasn't a -440 SQL error from a secure JDBC reported in Detector?

book

Article ID: 192878

calendar_today

Updated On:

Products

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

Issue/Introduction

An application passed bad arguments to a DB2 Native Stored Procedure using a secure JDBC. The failure was due to a -440 SQL error. Detector didn't  report the -440 error until the JDBC connection was changed from secure to unsecure. Why did Detector not capture the secure JDBC -440 SQL Error?

 

Environment

Release : 20.0

Component : CA Detector for DB2 for z/OS

Resolution

The SSL processing rejected the request due to an authentication failure, which results in the -440. Because the authentication failed, no DB2 activity occurred on the request, and therefore Detector never saw the error, as Detector was never invoked.