A SQLCODE -440 error from a secure JDBC is not reported in Detector

Products

• Detector for DB2 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 for Db2 for z/OS (PDT) did not report the SQL-440 error until the JDBC connection was changed from secure to unsecure.
Why did Detector not capture the secure JDBC -440 SQL error.

Resolution

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