Thank you. I had forgotten that instrumentation was implemented as its own 
command.

On 12/10, Andrew Raibeck wrote:
> Go to the link in my sig and do a search on:
>
>    performance tuning information
>
> Best regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
>
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/12/2009
> 07:58:58 AM:
>
> > [image removed]
> >
> > instrumentation for the server?
> >
> > km
> >
> > to:
> >
> > ADSM-L
> >
> > 10/12/2009 08:05 AM
> >
> > Sent by:
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Please respond to "ADSM: Dist Stor Manager"
> >
> > Hello,
> >
> > I am currently analyzing a TSM server which uses 100% CPU on 4 cores
> > when doing client backups. Almost all of it is privileged times, but
> > there are very few IO's and low disk queues for both stgpools, db and
> log.
> >
> > Are there any trace flags similar to the client testflag
> instrument:detail
> > but for the server that will allow me to see what the server is spending
> > time on?
> >
> > I've been looking in the problem determination guide but cant find any
> > flag similar to instrument_detail except for 'instr' which isnt
> documented
> > and only gives me DB LATCHes.
> >
> > -km