That is the purpose of the STROBE, GTF, ETC. step. You have to start someplace. The stuff under the covers is the fun part!
<snip> ---------------------------<snip>----------------------------- >Using SMF30 subtype 4 > >Calculate top 100 cpu consuming steps (Total of TCB/SRB) by program name (EXEC PGM=) over some period of time. >Add any appropriate filters and retry. E.G. IEBGENER - IBM code, can't do much about it in the short run, so ignore. > >Calculate for the top 100 CPU consumed/IO (excp count). >Rank the top 100 by CPU/IO. > >Start at the top of the list and work down using STROBE, GTF, other to determine the cause. > >Code/test/promote. > >Repeat ad infinitum, until be benfits gained are exceeded by the effort required. > >Hope this approach helps. > > ----------------------------<unsnip>---------------------------- This sounds good until you dig a little deeper. There's no record in SMF of any subroutines, etc. that are invoked via LINK or LOAD/CALL/DELETE or ATTACH or XCTL. This "little gap" can lead to a lot of missing formation. BTDTGTSS </snip> ---------------------------------------------------------------------- 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
