Hello Paul,

I just got back from SHARE so I myself don't know right now whether discarding
the pruned entries will circumvent the problem. However, I can tell you that
the problem has been fixed and that we intend to refresh the 3.1.0.5 version of
the NT client soon, probably this week. The expiration problem with unicode
file names should also be fixed with this refresh. Hopefully you can hold off a
little bit (?).

Either I or someone else will post to ADSM-L when the refreshed Win32 client is
available for download.

Best regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 08/24/98 07:40:17 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Win32 client bug!!


Can someone tell me if this problem be circumvented by specifying that
pruned log entries are to be Discarded?  I.e.,

SCHEDLOGRETENTION 30 D

The APAR does not indicate anything about this, but I figured if the
problem has to do with the pruning log getting too large that specifying a
"D" to discard the pruned entries might just be a workaround.

We unfortunately need to deploy a V3 NT client (for NT servers that backup
Mac filespaces).  We view this bug as a serious one, and not pruning the
log file will lead to other problems on the server.

Thanks.
..Paul

PS: I don't have an NT system handy to try this on, or I'd have tried it
myself!
--
At 10:21 AM 8/19/98 -0400, you wrote:
At 10:21 AM 8/19/98 -0400, you wrote:
>It's a known problem. Please turn off schedule log pruning for now until
we can
>get it fixed.
>
>Pete Tanenhaus, ADSM NT Client Development
>---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 08/19/98
>10:08 AM ---------------------------
>
>
>ADSM-L AT VM.MARIST DOT EDU on 08/19/98 03:30:03 AM
>Please respond to ADSM-L AT VM.MARIST DOT EDU
>To: ADSM-L AT VM.MARIST DOT EDU
>cc:
>Subject: Win32 client bug!!
>
>
>Dear ADSM-ers!
>This is a warning for all Windows 32 client 3.1.05 users!
>If you use the dsmsched.log pruning option this can cause your filespace to
>fill up completely.
>Yesterday I installed the 3.1.05 client on 3 Windows NT machines. After the
>backup the ADSM scheduler starts pruning the dsmsched.log which never
>finishes. It created a dsmprun.log which took up all the available free disk
>space!
>This sounds like a serious bug in the ADSM client code.
>Kindest regards,
>Eric van Loon
>
>
>
>