You also have to stop and restart the client scheduler after making a change 
for it to become effective.

David B. Longo
Systems Administrator
Health First, Inc. I/T
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH      321.434.5536
Pager  321.634.8230
Fax:    321.434.5525
david.longo AT health-first DOT org



>>> Larry_Clark AT THRUWAY.STATE.NY DOT US 12/22/00 02:32PM >>>
I believe D is the default

>>> David.Longo AT HEALTH-FIRST DOT ORG 12/22/00 02:32PM >>>
I believe that you have to have the units for retention  (D for days)

All my entries are like:
ERRORLOGRETENTION 7,D

If you don't have the line at all then there is no purge as I found a server 
that had a 200MB sched.log!!

David B. Longo
Systems Administrator
Health First, Inc. I/T
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH      321.434.5536
Pager  321.634.8230
Fax:    321.434.5525
david.longo AT health-first DOT org 



>>> Larry_Clark AT THRUWAY.STATE.NY DOT US 12/22/00 01:56PM >>>
Hi:
Despite having these entries in the dsm.opt TSM does not purge older entries in 
the dsmerror.log  & dsmsched.log in the 4.1.1 client. Anyone else seen this?

SCHEDLOGNAME "C:\WIN32APP\IBM\ADSM\baclient\dsmsched.log"
ERRORLOGNAME "C:\WIN32APP\IBM\ADSM\baclient\dsmserror.log"
SCHEDLOGRETENTION 7
ERRORLOGRETENTION 7

Larry Clark
NYS Thruway Authority