[DB2 V8 NFM z/OS] Explain STMTCACHE

Walter Janißen

[DB2 V8 NFM z/OS] Explain STMTCACHE
Hi

I just read the information letter on PQ88073, but I didn't understand
everything. I created all the necessarey tables and executed the statement
EXPLAIN STMTCACHE ALL. So I got the DSN_STATEMENT_CACHE_TABLE filled up
with some rows. But all the counters are 0. Other columns, like Timestamp-
columns are filled. What do I miss? Why are all counters 0?

When I explain a single statement with a STMTID picked up from the previous
explain, I got an error-message:

SQLCODE = -20248, ERROR: ATTEMPTED TO EXPLAIN ALL CACHED STATEMENTS OR A
CACHED STATEMENT WITH STMTID OR STMTTOKEN 374287 BUT THE REQUIRED EXPLAIN
INFORMATION IS NOT ACCESSIBLE

Again: What do I miss?

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Jim Mourgelas

Re: [DB2 V8 NFM z/OS] Explain STMTCACHE
(in response to Walter Janißen)
Hi,

IFCID 318 must be activated to populate counters. If there is any
significant time delay between the issuing of EXPLAIN STMTCACHE ALL and
EXPLAIN STMTCACHE STMTID token then it is possible that the cached
statement with the given token has been freed from the statement cache.



Jim Mourgelas
IT Specialist, Database Technical Services
zServer Engineering
TD - Infrastructure Technology Solutions
TD Bank Financial Group
Phone: 416-982-2879
Fax : 416-982-4527
e-mail: [login to unmask email]



Walter
Janißen
<walter.jan To
[login to unmask email] [login to unmask email]
RIA.DE> cc
Sent by:
DB2 Data Subject
Base [DB2-L] [DB2 V8 NFM z/OS] Explain
Discussion STMTCACHE
List
<[login to unmask email]
DB2-L.ORG>


12/11/2006
10:24 AM


Please
respond to
DB2
Database
Discussion
list at
IDUG
<[login to unmask email]
IDUGDB2-L.O
RG>






Hi

I just read the information letter on PQ88073, but I didn't understand
everything. I created all the necessarey tables and executed the statement
EXPLAIN STMTCACHE ALL. So I got the DSN_STATEMENT_CACHE_TABLE filled up
with some rows. But all the counters are 0. Other columns, like Timestamp-
columns are filled. What do I miss? Why are all counters 0?

When I explain a single statement with a STMTID picked up from the previous
explain, I got an error-message:

SQLCODE = -20248, ERROR: ATTEMPTED TO EXPLAIN ALL CACHED STATEMENTS OR A
CACHED STATEMENT WITH STMTID OR STMTTOKEN 374287 BUT THE REQUIRED EXPLAIN
INFORMATION IS NOT ACCESSIBLE

Again: What do I miss?

---------------------------------------------------------------------------------

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org
. The IDUG List Admins can be reached at [login to unmask email]
Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm



********************
NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is
intended only for the use of the addressees and is confidential.
If you are not an intended recipient or responsible for delivering
the message to an intended recipient, any review, disclosure,
conversion to hard copy, dissemination, reproduction or other use
of any part of this communication is strictly prohibited, as is the
taking or omitting of any action in reliance upon this communication.
If you receive this communication in error or without authorization
please notify us immediately by return e-mail or otherwise and
permanently delete the entire communication from any computer,
disk drive, or other storage medium.

If the above disclaimer is not properly readable, it can be found at
www.td.com/legal

AVERTISSEMENT DE CONFIDENTIALITE
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
aux destinataires susmentionnés, est confidentiel. Si vous
n’êtes pas le destinataire prévu ou un agent responsable de la
livraison de ce courriel, tout examen, divulgation, copie, impression,
reproduction, distribution, ou autre utilisation d’une partie de ce
courriel est strictement interdit de même que toute intervention ou
abstraction à cet égard. Si vous avez reçu ce message par erreur ou
sans autorisation, veuillez en aviser immédiatement l’expéditeur par
retour de courriel ou par un autre moyen et supprimer immédiatement
cette communication entière de tout système électronique.

Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
pouvez le consulter à www.td.com/francais/legale

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Brenda Henley

DB2 V8 NFM
(in response to Jim Mourgelas)
We are planning to go from DB2 V8 CM to NFM next quarter. I started
contacting the OEM Vendors for impacts and see if their products exploit
NFM. Does anyone have any experiences they can share on this area? Thanks

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Infodemic B.V. Douwe van Sluis

Re: DB2 V8 NFM
(in response to Brenda Henley)
Brenda,

Make sure you know what you need from V8 and focus on those items.
Do not forget IBM product for their ability to exploit!! V8. Omegamon 5.40
is able to tolerate V8, but is not able to exploit V8.

Vriendelijke groet,
Douwe van Sluis, Infodemic B.V.


-----Oorspronkelijk bericht-----
Van: DB2 Data Base Discussion List [mailto:[login to unmask email] Namens
Brenda Henley
Verzonden: dinsdag 12 december 2006 19:29
Aan: [login to unmask email]
Onderwerp: [DB2-L] DB2 V8 NFM

We are planning to go from DB2 V8 CM to NFM next quarter. I started
contacting the OEM Vendors for impacts and see if their products exploit
NFM. Does anyone have any experiences they can share on this area? Thanks

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm