The SQL_CALL info differs between R14.0 and R20.0 PDT.

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

いつもお世話になっております。

本田技研 和光事業所 オペレーションGr.山村です。

弊社では、8月18日に開発区画のバージョンアップを実施し、DB2 v9からv12 へマイグレーションを実施し併せて、DB2v9ではDETECTORはR14版を使用しておりましたが、R20版を新規導入しております。

業務プログラムのバージョンアップ前後でのパフォーマンスをDETECTORを使用し比較しておりますが、R14とR20でのSQL_CALL表記に差異があります。

※ 処理タイプは、SQLJでのアクセスになります。

v9では、OPEN,FETCH,DESCRIBE    →   v12では、OPEN,COMMIT

v9では、OPEN,FETCH,DESCRIBE   →   v12では、OPENのみ

v9では、OPEN,FETCH,DSCRIBE   →    v12では、OPEN,FETCH,COMMIT

 

プログラムの動作に変化があるわけではなく問題なく稼働してしておりますが、SQL_CALL表記の仕様変更についてご教授頂けますでしょうか。

もし、パラメータ設定値等の問題であれば、お知らせください。

以上

よろしくお願いします。

English;

 

The client upgraded their z/OS from V2.1 to V2.3 and also upgraded their Db2 from V9 to V12. So, he newly installed R20.0 Detector and Plan Analyzer in their z/OS 2.3 system and applied published PTFs to them. (They were using R14.0 Detector and Plan Analyzer in their z/OS 2.1 system. They didn't upgrade their R14.0 to R20.0 but they installed R20.0 newly in their z/OS 2.3 system.)

 

The client said that the SQL_CALL info is different between R14.0 and R20.0.   He said that the difference seems to be only in SQLJ type. 

 

 

In their R14.0 PDT(DB2 V9), the SQL_CALL info was "OPEN,FETCH,DESCRIBE". In their R20.0 PDT (DB2 V12), the SQL_CALL info of the same SQL is "OPEN,COMMIT".

In other SQL, in their R14.0 PDT(DB2 V9), the SQL_CALL info was "OPEN,FETCH,DESCRIBE". In their R20.0 PDT (DB2 V12), the SQL_CALL info of the same SQL is "OPEN" only. 

In other SQL, in their R14.0 PDT(DB2 V9), the SQL_CALL info was "OPEN,FETCH,DESCRIBE". In their R20.0 PDT (DB2 V12), the SQL_CALL info of the same SQL is "OPEN,FETCH,COMMIT ". 

 

He doesn't understand why the SQL_CALL info are different between R14.0 and R20.0. 

 

Environment

Release : 20.0

Component : CA Detector for DB2 for z/OS

Resolution

What the customer sees is explained by the difference between DB2V9 and DB2V12.

Between these two releases IBM made a lot of changes for in the processing distserv which the SQLJ falls under. Either in DB2V10 or DB2V11 IBM introduces the change for the COMMIT intercept and as you know we update the products to keep up with IBM changes.

because of that Detector now processes the COMMIT which Detector didn't do in the past.