Salam,

Strange, have a look if your environment variable DSM_DIR is set to
/usr/lpp/adsm/bin.  The other reason could be that ADSM is not able to
write to the /usr/lpp/adsm/bin directory.

Regards
Gerrit van Zyl

ABDULSALAM ABDULLA wrote:

>         I realized that the dsmsched.log is being created and getting
> updated under root directory despite this entry "schedlogname
> /usr/lpp/adsm/bin/dsmsched.log" in dsm.sys.   Any idea?
>
> Thanks,
> Salam
>
> > -----Original Message-----
> > From: Gerrit van Zyl [SMTP:gvanzyl AT FARITEC.CO DOT ZA]
> > Sent: Monday, August 23, 1999 11:39 AM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: dsmsched.log is not updating
> >
> > Salam,
> >
> > Have a look if the user under which ADSM Server is running, has got
> > read-write access to the dsmsched.log file.
> >
> > Regards
> > Gerrit van Zyl
> >
> > ABDULSALAM ABDULLA wrote:
> >
> > > Just upgraded ADSM from ver 2 to ADSM Server for AIX-RS/6000 -
> > Version
> > > 3, Release 1, Level 2.40.  Client is 3.1.06
> > > Since upgrade I noticed that dsmsched.log is not getting updated.
> > All
> > > of the entries in dsmsched.log are old.
> > > following is the entries in my "dsm.sys"
> > >
> > > SErvername      adsm-server-itb
> > >  COMMMETHOD     TCPIP
> > >  TCPPORT        1500
> > >  TCPSERVERADDRESS       172.20.39.09
> > >  INCLEXCL       /usr/lpp/adsm/bin/excludefile
> > > * passwordaccess generate
> > >  passwordaccess prompt
> > >  nodename       itb_adsm
> > >  COMPression    YES
> > >  schedlogname   /usr/lpp/adsm/bin/dsmsched.log
> > >  errorlogname   /usr/lpp/adsm/bin/dsmerror.log
> > >
> > > What could be the problem.
> > >
> > > Thanks,
> > > Salam << File: Card for Gerrit van Zyl >>