Yes, I too had this problem.  I created a Mgmt. Class which I called
'LargeFileChanging' (you can call it what you want).  It has the CopyGroup set
to have "Copy Serialization: Dynamic".   This way the files will be backed up
on the first pass of reading the file, regardless of it changing.  Then in the
include/exclude list I include the dsmcsched.log with the setting the MC to
'LargeFileChanging'.
        include /.../dsmsched.log               LargeFileChanging

I also include other log file that might be changing during backup in this
managment class.  This has solved the problem for me.  I hope it helps you.

Chuck T.

>Date:    Thu, 9 Jul 1998 06:44:36 -0400
>From:    Gene Mangum <gmangum AT UMICH DOT EDU>
>Subject: dsmsched.log changed
>
>Hi All,
>
>Since I upgraded clients and server to v3, one node has consistently
>been refusing to backup dsmsched.log, saying that it has changed during
>the backup.   This results in the backup status being "Failed".   This
>is not hapenning on the other nodes (except one other last night), and
>it never happened on v2.   I know I could put this file in the exclude
>list, but I kinda like having it backed up.   Has anyone else seen this?
>
>Gene Mangum
>University of Michigan Medical Center