This is a bug that will be fixed in PTF 3.  I forced the msgmode to QUIET in
the service with the intent of disabling server offline media aborts without
realising that QUIET also suppresses output to the schedule log. Until you get
the ptf, there is an undocumented registry setting that *may* get around the
problem for now. Use this option at your own risk.

Under the the following registry hierarchy where <ADSM Client Service> is the
name of the service :

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<ADSM Client Service
Name>\Parameters

add a REG_SZ  value named ClientCmdLine to be a string as follows:

-VERBOSE
This registry setting can be used to pass any valid command line argumeThis 
registry setting can be used to pass any valid command line argument
string to the scheduler thread (essentially the same as passing command line
arguments to dsmc).

Hope this helps ......

Pete Tanenhaus
ADSM NT Client Development
---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 02/06/98
6/98
11:38 AM ---------------------------

        ADSM-L AT VM.MARIST DOT EDU
        02/06/98 09:59 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet

To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
Subject: Re: Scheduler as NT service. Logging question

I have noticed the same thing.  One thing I tried was to turn on VERBOSE
mode but it still doesn't log individual files in the DSMSCHED.LOG file
that are being backed up.  How do we turn this back on?  It was working
in the old version 2 clients.

        Jim