Hilton Tina writes:
 > What's the platform?  In AIX, the include/exclude statements must be in
 > a separate file that is pointed to in dsm.sys with the Inclexcl
 > statement.  The actual include statements would also be helpful.  If you
 > added the inclexcl to dsm.sys, did you also bounce the scheduler?  That
 > needs to be done so it will know there is an include/exclude file.
 >

The server is on AIX. The clients are on HPUX, Xopen/ADSM for
Informix, Linux and Novell. Only for Novell the include/exlude
statements are int the dsm.opt file. On the Unix plattforms they are
in a separate file.

The statements are
on Novell:

INCLUDE progs:\...\*.*  NOVELL_PROGRAMME

on hp-ux for Informix:

INCLUDE /snoopy2_online/.../* INFORMIX

As I said, they work for dsmc inc but not for dsmc schedule

Christoph

 >
 >Christoph Martin writes:
 > >
 > > Hi all,
 > >
 > > We want to use different management-classes to specify how
 > many
 > > backup-versions should be kept by ADSM for different
 > filesystem.
 > >
 > > For programms there are two versions to be kept, for data
 > three
 > > versions.
 > >
 > > The three versions are specified in the default management
 > class. We
 > > defined an aditional class for the programms and added
 > includes lines
 > > in dms.sys with the classes.
 > >
 > > Everything works if the backup command is invoked from the
 > client with
 > > dsmc inc ...
 > > But if you use a schedule to backup and start
 > > dsmc schedule
 > > all files are backuped with standard management class.
 > >
 > > What is the problem?
 > >
 >
 >Forgot to say:
 >
 >Server is version 2 or 3. Clients are version 2 or 3.
 >
 >Christoph
 >