STROBE does have a DB2 component but you have to pay for it. Once you have it, it will identify the cost by SQL statement. DB2 SMF records are a much higher level reporting. They will show IO, cpu by package (program) but not by sql statement. You can do the iebeyeball method and watching the program run with a DB2 monitor and see which statement is active most of the time. That does work more often than not but the core problem is probably an access path problem which will require SQL tuning knowledge.
Mike On 4/21/06, Ted MacNEIL <[EMAIL PROTECTED]> wrote: > > >They asked for a Strobe trace which says Extended Cross memory access is > eating up most of the CPU time. Any guess on what could be the reason. > > It's inside DB2 from the looks of things (DSN* as a routine name). > It's not reporting what is happening once the programme accesses DB2. > Just billing it as cross-memory is insufficient to answer the question. > You need to trace the DB2 activity, somehow. > Does STROBE have a DB2 component? > > > - > -teD > > O-KAY! BLUE! JAYS! > Let's PLAY! BALL! > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- Mike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
