ADSM-L

Windows client 3.1.0.7 problem

2000-02-04 13:08:00
Subject: Windows client 3.1.0.7 problem
From: Terry Phelps <terryp AT ACBL DOT NET>
Date: Fri, 4 Feb 2000 13:08:00 -0500
We recently upgraded our Windows clients from version 3.1.0.6 to 3.1.0.7,
and immediately noticed two problems, possibly related, with the
dsmsched.log file:

1. Even though our dsm.opt file says to retain 21 days of schedule log
information, it is being truncated to only ONE day of information. This did
NOT happen with 3.1.0.6.

2. The dsmsched.log is being somewht corrupted. For instance, here is how
the beginning of my dsmsched.log file looks:

00 21:44:22 Schedule Log Prune: 689 lines processed.  408 lines pruned.
00 21:44:22 ANS1484I Schedule log pruning finished successfully.
00 21:44:22 Querying server for next scheduled event.
00 21:44:22 Node Name: NTSERVER50
00 21:44:22 Session established with server ACBL-JFV-ADSM: Windows NT
00 21:44:22   Server Version 3, Release 1, Level 2.50
00 21:44:22   Server date/time: 02/02/2000 21:44:22  Last access: 02/02/2000
21:30:12
00 21:44:22   Server date/time: 02/02/2000 21:44:22  Last access: 02/02/2000
21:30:12
00 21:44:22 --- SCHEDULEREC QUERY BEGIN
00 21:44:22 --- SCHEDULEREC QUERY END

See how the date part of the date/time stamp is mostly missing?  Now here's
the end of my dsmsched.log file, showing where this corruption ends, and
good timestamps begin:

00 21:42:19 Results sent to server for scheduled event 'WEEKDAY'.
00 21:42:19 ANS1483I Schedule log pruning started.
02/03/2000 21:42:19 Schedule Log Prune: 631 lines processed.  281 lines
pruned.
02/03/2000 21:42:19 ANS1484I Schedule log pruning finished successfully.
02/03/2000 21:42:19 Querying server for next scheduled event.
02/03/2000 21:42:19 Node Name: NTSERVER50
02/03/2000 21:42:19 Session established with server ACBL-JFV-ADSM: Windows
NT
02/03/2000 21:42:19   Server Version 3, Release 1, Level 2.50
02/03/2000 21:42:19   Server date/time: 02/03/2000 21:42:19  Last access:
02/03/2000 21:30:12

02/03/2000 21:42:19 --- SCHEDULEREC QUERY BEGIN
02/03/2000 21:42:19 --- SCHEDULEREC QUERY END
02/03/2000 21:42:19 Next operation scheduled:
02/03/2000
21:42:19 ------------------------------------------------------------
02/03/2000 21:42:19 Schedule Name:         WEEKDAY
02/03/2000 21:42:19 Action:                Incremental
02/03/2000 21:42:19 Objects:
02/03/2000 21:42:19 Options:
02/03/2000 21:42:19 Server Window Start:   21:30:00 on 02/04/2000
02/03/2000
21:42:19 ------------------------------------------------------------
02/03/2000 21:42:19 Waiting to be contacted by the server.

We can live with the date corruption, but we'd really like to retain more
than the one day of schedule log information. Can anyone assist?
<Prev in Thread] Current Thread [Next in Thread>