Trace tool : st12 - not capturing properly

[giri_raaj]

HI guys,

I am using st12 transaction for tracing my progarm module wise time consumption.

my program takes 3000 seconds. for completing the job.

i would like to know where it takes more time.... i used the tcode st12.

i am not getting correct result.....from st12.....

i suspect something wrong with this tool...how can i set it right......

regards

girish

[ThomasZloch]

"not getting correct result", "something wrong", this is all very vague, please disclose many more details about the problem if you expect meaningful help.

Have you tried using SAT or SE30 instead, maybe all the functions that ST12 offers are not necessary for your analysis.

Thomas

[HermannGahm]

Hi Giri,

as Thomas said, please provide more details.

what kind of process have you traced and what trace options did you use:

dialog execution ? (current mode)

background job ? (schedule trace, tasks & http)

incoming rfc? (task & http)

...?

Kind regards,

Hermann

[giri_raaj]

HI ....

thanks for your reply.

Program run for 3000 seconds...... st12 trace shows

abap time : 100 seconds

system time : 10 seconds

db time : 120 seconds

i ran the program by background , i selected current mode : and given type : BTC., Provided my userid also.

Since the variation is very high....(210 seconds -....original run time was 3000 seconds)

please provide your inputs on the same, if my execution procedure is wrong...correct me.

regards

giri

[HermannGahm]

Hi Giri,

sound you used the USER scenario (not the current mode).

It's not recommended to use the USER scenario anymmore.

Instead use the task & http scenario explained here:

/people/hermann.gahm/blog/2010/03/22/st12-150-tracing-user-requests-tasks-http

with BTC filter or schedule a trace. In ST12 - Utilities - Schedule Trace - For Workprocess or Dialog Task.

(not documented yet). Check Interval should be 10, Trace duration should be 3600 or so.

don't forget to switch on the internal tables before you jump to the dialog mentioned above.

Try with these options.

Kind regards,

Hermann

[yuri_ziryukin]

> It's not recommended to use the USER scenario anymmore.
> Instead use the task & http scenario explained here:

Hello Hermann,

by the way, why? I am not aware of this.

Used "USER" scenario yesterday in the previous release (01M). Had a problem that the first recorded and collected trace was ofc. from the ST12 itself, but when I went to "collect ext. traces" I was able to find the second ABAP trace from the mode where I was executing my real transaction. As far as I know from Bernd, technically these two options work in the same way.

Yuri

[HermannGahm]

Hi Yuri,

> > It's not recommended to use the USER scenario anymmore.

> > Instead use the task & http scenario explained here:

>

> by the way, why? I am not aware of this.

> Used "USER" scenario yesterday in the previous release (01M). Had a problem that the first recorded and collected trace was ofc. from the ST12 itself, but when I went to "collect ext. traces" I was able to find the second ABAP trace from the mode where I was executing my real transaction. As far as I know from Bernd, technically these two options work in the same way.

Well, simply because it is not as transparent (manual collection and so on). Because it is the user scenario is the same but not as transparent as the task & http (and has additional efforts with manual collection) i think it will disappear (or better put together or replaced with task & http) in the next version (as far as i know). Im my opinion the user mode is kind of obsolete because it is only a subset of the task & http secario without any additional advantage.

Kind regards,

Hermann

Edited by: Hermann Gahm on Jun 16, 2011 10:49 AM