You could always add the DSM_* environemtn variables to the client node.

DSM_DIR=
DSM_CONFIG=

and add the DSM_DIR to the PATH variable. There is a section in the Windows
B/A client manual titles "Setting environment variables" that describe
these. One of the reasons listed is:

"1. You want to invoke Tivoli Storage Manager from a directory other than
the directory where Tivoli Storage Manager is installed."

If you set these variables for the System-level you can then use the
original command "DSMC BACKUP ..." wihtout having to code up a .BAT file
which CD's to the directory. Cuts out some steps, but works just the same.

Bill Boyer
"Life is not about how fast you run,
or how high you climb
but how well you bounce." - ??



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Hart, Charles
Sent: Tuesday, June 01, 2004 5:26 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Separating Windows System Object Backup from the File
system Backups


Fantastic!!!!!  That worked just Great!  Makes sense as the TSM Server
Scheduler contacts the TSM Client API which should know what Dir its in...
Dahhh!

Thanks !

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Rushforth, Tim
Sent: Tuesday, June 01, 2004 4:13 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Separating Windows System Object Backup from the File
system Backups


We've done similar things in the past (registry backups, event log backups)
without specifying a path at all on the schedule.

Have you tried just dsmc backup systemobject for the objects?

-----Original Message-----
From: Hart, Charles [mailto:charles.hart AT MEDTRONIC DOT COM]
Sent: June 1, 2004 3:33 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Separating Windows System Object Backup from the File system
Backups

We've been having issues with the log being pinned by Win2k Sysobj's  The
Tivoli tech support had me create two schedules (One for File system only
and one set of Scheds for Sysobj.)  If anyone has any ideas that would be
great!  We want to do this from the server side as we have hundreds of Intel
rabbits.

File System Only Sched - Which Works fine
define schedule <domainname> <schedulename> action=incremental
options="-domain='-systemobject'"

Win2k SysObj Sched - Can not get to work our path is slightly different (IE
c:\program fiule etc)
define schedule <domainname> <schedulename>
action=commandobjects='c:\tsm\baclient\dsmc backup systemobject'

Our Sysob Sched Detail

 Policy Domain Name: INTEL
                Schedule Name: INTEL_SYSOBJ
                  Description:
                       Action: Command
                      Options:
                      Objects: C:\Program Files\Tivoli\TSM\baclient\dsmc
backup systemobject
                     Priority: 5
              Start Date/Time: 06/01/04   15:20:00
                     Duration: 1 Hour(s)
                       Period: 1 Day(s)
                  Day of Week: Any


Detail from dsmsched log...

2004-06-01 15:20:03 --- SCHEDULEREC QUERY BEGIN
2004-06-01 15:20:03 --- SCHEDULEREC QUERY END
2004-06-01 15:20:03 Next operation scheduled:
2004-06-01 15:20:03
------------------------------------------------------------
2004-06-01 15:20:03 Schedule Name:         INTEL_SYSOBJ
2004-06-01 15:20:03 Action:                Command
2004-06-01 15:20:03 Objects:               C:\Program
Files\Tivoli\TSM\baclient\dsmc backup systemobject
2004-06-01 15:20:03 Options:
2004-06-01 15:20:03 Server Window Start:   15:20:00 on 2004-06-01
2004-06-01 15:20:03
------------------------------------------------------------
2004-06-01 15:20:03
Executing scheduled command now.
2004-06-01 15:20:03
Executing Operating System command or script:
  C:\Program Files\Tivoli\TSM\baclient\dsmc backup systemobject
2004-06-01 15:20:03 Finished command.  Return code is: 1
2004-06-01 15:20:03 ANS1909E The scheduled command failed.
2004-06-01 15:20:03 ANS1512E Scheduled event 'INTEL_SYSOBJ' failed.  Return
code = 1.
2004-06-01 15:20:03 Sending results for scheduled event 'INTEL_SYSOBJ'.
2004-06-01 15:20:03 Results sent to server for scheduled event
'INTEL_SYSOBJ'.

DSMERROR Log
2004-06-01 15:20:03 ANS1909E The scheduled command failed.
2004-06-01 15:20:03 ANS1512E Scheduled event 'INTEL_SYSOBJ' failed.  Return
code = 1.

TSM Env
Server AIX 5.2.2 TSM 5.2.4
Client WIn2k TSM Client 5.2.2


Thank You!