View previous topic :: View next topic
|
Author |
Message |
manojtyagi_09
New User
Joined: 30 Oct 2006 Posts: 10
|
|
|
|
Hi
I am getting the message "Very FEW samples" when doing strobe for a Program in which a cursor fetches the record from Db2 table and writes to output file.
The table contain 2400 records.
Can anyone inform what can i do to get the report with this set of records.
Min session Duration : 1 min
Target sample size : 10000 >> i tried it with 100, 1000 also but same error. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Suggest you look in the Strobe documentation or talk with your systems support person/people who support Strobe.
Your situaton appears to involve Strobe more than DB2, so i moved your topic to the Compuware part of the forum. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
|
|
|
|
Strobe needs a minimum number of samples to accurately portray the program execution status. The message you're getting indicates Strobe isn't collecting enough samples for accuracy. You can tell Strobe a better estimate of the run time, or merely be aware that your results that Strobe shows may not be reproducible across multiple runs. |
|
Back to top |
|
|
mike duff
New User
Joined: 05 Mar 2009 Posts: 4 Location: halifax
|
|
|
|
manojtyagi_09 wrote: |
Hi
I am getting the message "Very FEW samples" when doing strobe for a Program in which a cursor fetches the record from Db2 table and writes to output file.
The table contain 2400 records.
Can anyone inform what can i do to get the report with this set of records.
Min session Duration : 1 min
Target sample size : 10000 >> i tried it with 100, 1000 also but same error. |
The last shop I worked in required 100,000 sample size to make the strobe statistically correct (error < 2% & <10%) |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
A technique that I used when encountering the same problem:
I coded a 'loop' in the program controlled by PARM:
if the PARM was not there, then the loop was 1,
otherwise I performed the program 10,000 times.
just put code at the beginning of your program that effectively performs your 'existing program'. the only thing that you miss is the db2 code at the begining that sets up addressability for db2 and host variables. |
|
Back to top |
|
|
|