Kyle

Your email sparked off my curiosity and I started to look at tracing. I
found a nice manual: "ADSM Trace Facility Guide" on the CD.

About your problem it says in this manual:
"When you enter trace options from the command line or in the options file,
 we
recommend the following sequence:
   1.TRACEMAX
   2.TRACEFILE
   3.TRACEFLAGS
Following this order will ensure that all trace entries from the start of
the trace will
go into the file that you specify. "

It sounds like when you specify the traceflags, it starts tracing, whether
you have specified a tracefile or not.

But now I have a question for you. Do you have a description of the meaning
of the output of INSTR_CLIENT_DETAIL. It looks that gives a summary of how
the time was spent during a session. I could use this information for
tuning and to find bottlenecks. Some of the section names are descriptive,
but others I cannot figure out what they mean.

Thanks
     Geetam

>

> Date:    Tue, 2 Nov 1999 13:56:22 -0600
> From:    Kyle Payne <payne AT BERBEE DOT COM>
> Subject: Goofy Thing with Traces
> MIME-Version: 1.0
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
>

>         In the Advance ADSM class we realized the benefit of using the
> INSTR_CLIENT_DETAIL so we starting using it on many of our clients.  For
a
> short time some one had the order for the trace settings as follows:
> TRACEFLAGS              INSTR_CLIENT_DETAIL
> TRACEFILE               "C:\Program Files\IBM\ADSM\DSMTRACE.LOG"
> TRACEMAX                25
>
>         When the settings are in this order, which we now believe to be
in
> correct,
> the file we specify isn't used.  It is created and date and time stamps
are
> placed in it when we start and stop the scheduler service but the actual
> trace information isn't there.  Instead a file called Program at C:\ is
> created.  In it is the ADSM trace information.  We have since changed
> theorder to:
> TRACEMAX                25
> TRACEFILE               "C:\Program Files\IBM\ADSM\DSMTRACE.LOG"
> TRACEFLAGS              INSTR_CLIENT_DETAIL
>
>         Having the settings in this order solves the problem.
>
>         The file C:\Program was causing problems for other applications
> though.  PC
> Anywhere was hanging on the file.  Also some proxy servers were going
down
> as a result of it.  I am opening a call with IBM to see why it just picks
a
> file called C:\Program.
>
>         Have you seen this?  Can you recreate it?  It is pretty easy to
> recreate.
> Just copy the top set of trace settings to your dsm.opt file.  Stop and
> start the scheduler service and look for a file called C:\Program.  In it
> will be your trace information.
>
>
>
> Thanks,
>         Kyle
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Kyle Payne
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>

______________________________________________________________________
CONFIDENTIALITY NOTICE:  This message is confidential and for the use only
of the intended recipient.  If you receive the message in error you are not
entitled to disseminate, copy or use the contents in any way.  In such
circumstances please forward the message back to the sender or contact
Scottish Provident Institution by telephone on 0131 556 9181.

Scottish Provident UK is the marketing name in the UK of The Scottish
Provident Institution, (a mutual life office incorporated by Act of
Parliament registered in Scotland no. Z5).  It is a member of the Scottish
Provident marketing group which also includes Scottish Provident
International Life Assurance Limited (registered in the Isle of Man no.
053002C).  Both companies are regulated by the Personal Investment
Authority.  Scottish Provident Trustees Limited, (registered in Scotland
no. 108046), Scottish Provident Pension Trustees Limited* (registered in
England no. 2404622). Registered Office: 7-11 Melville Street, Edinburgh,
EH3 7YZ. *Registered Office: One Silk Street, London, EC2Y 8HQ.   Head
Office: 6 St Andrew Square, Edinburgh, EH2 2YA.  Telephone 0131 556 9181