That was a known bug in the 3.1.0.0 client.
Use a later version, 3.1.0.3 at least, preferably 3.1.0.6.

You can download it from the ADSM home page.
Go to www.storage/ibm/com/adsm.

At the top of the page, click the link "View the Latest".

Follow the links for "Most up to date Client Code",
then look in the table for MS Windows NT,

Click the link for IP20993.

That will take you right to the FTP server for downloads.

Install it right over top of the 3.1.0.0 client.
Fixes a lot of other bugs, too.

***************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
***************************************************************




> -----Original Message-----
> From: David Matthews [SMTP:dmatthew AT HIH.COM DOT AU]
> Sent: Thursday, January 21, 1999 7:08 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      DSMSCHED.LOG lacking detail
>
> Hi,
>
> I have an NT Server 4.0 running ADSM 3.1.0.0 Client, backing up to a AIX
> 2.1.5 Server
>
> The backup schedule has been setup via the 'dsmcutil.exe' command
> utilising
> the 'eventlogging=yes' switch.
>
> However the level of detail in the dsmsched.log file is minimal. It only
> records the successful backup of the registry and then any subsequent
> file/directory failures, then the backup summary information. (see
> attachment)
>
> If I run the scheduler as a foreground NT window, then it generates a
> detailed log file showing all registry, file and directory events for that
> operation. This indicates to me that there is not 'quite' mode set in the
> option file or on the ADSM server it's self
>
> Is there something I have missed is regards to getting the backup schedule
> running as an NT service, to record ALL events to the log??
>
> Ta.
>
> David Matthews
>
> (See attached file: samplog.txt) << File: Text - character set unknown >>