I've already seen this kind of problem with a Unix client. The schedule
did not perform completely if several drive arguments were passed to the
'dsmc incr' command. Have you tried to split your DSM.OPT 'domain'
option into 3 lines, like this : 

domain c:
domain d:
domain e:

Didier Rauw
Electrabel
dép. informatique, exploitation des systèmes distribués
Bd du Régent 8, 1000 Bruxelles
Tél. 02/518.65.48 - Fax. 02/518.62.97

>----------
>From:  Christo Heuer[SMTP:christoh AT ABSA.CO DOT ZA]
>Sent:  Wednesday, February 04, 1998 12:02 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       ADSM ignoring drive?
>
>Hi all,
>
>I have this unusual problem with ADSM ver 2.1.06 on WinNT.
>Server is ADSM MVS v2.1.13
>The machine has three drives c:,d: and e:
>No mirroring or anything funny - just straight forward NTFS.
>With the GUI or command line the backup does all the drives - no
>additional parameters are passed in the command line incr. - just
>a dsmc incr.
>The moment I use the scheduler to kick of the backup the third drive
>is ignored. When I look at the dsmsched.log it shows that the incr backup
>completed successfully with drive d: as the last drive. No further error
>messages or anything.
>
>I also tried the Version 3.0.1 code of ADSM but get exactly the same
>results.
>
>Has anyone encountered something like this before?
>
>Thanks in advance
>
>Christo Heuer
>ABSA Group
>Johannesburg
>South Africa
>