Hi John,
Try this. In DSM.OPT can you set a pre/post script.
Because of your TSM Schedule service is probably running System Account. 

System Account have no access to any network shares even if you set the network 
shares to Everyone full access.

What you need to do is setup a script next to TSM that login to the share with 
another user accout or change the TSM Schedule services to use a user account 
instead of System Account.

Here is an example a script can look like

******** Pre-script**********
@Echo off
net use b: \\myserver\share$ /user:myserver\username password
******** Pre-script**********

******** Post-script**********
@Echo off
net use b: /del
******** Post-script**********

If I where you I should run one script where you do everything direct, then 
should the script something like this.

******** Pre-script**********
@Echo off
net use b: \\myserver\share$ /user:myserver\username password
cd /d "C:\Program Files\Tivoli\TSM\BaClient"
dsmc i b:\ -subdir=yes
net use b: /del
******** Pre-script**********

Good Luck

Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: Christian.Svensson AT cristie DOT se
Skype: cristie.christian.svensson
________________________________________
Från: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] för Schneider, 
John [John.Schneider AT MERCY DOT NET]
Skickat: den 5 december 2008 22:27
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: Backup of share will not work with schedule

Greetings,
    I have a server that I can't install the TSM client on because the
vendor who owns it won't permit it.   One alternative seemed to be to
share the directory that must be backed up, and acces that share from
another server to back it up explicitely as an object.   We created a
share on that server that we can access from another server.
    I can log in to the other server, bring up the TSM line mode client,
and back it up with:

dsmc inc \\172.17.16.101\archive2\ -subdir=yes

And that backs up fine.  But when I build a schedule with the
\\172.17.16.101\archive2\ <file://172.17.16.101/archive2/>  as the
object, it fails.  The dsmsched.log is below.  Does anyone know the
scheduler won't backup a filesystem that the linemode client backs up
fine?

12/04/2008 13:00:11 --- SCHEDULEREC QUERY BEGIN
12/04/2008 13:00:11 --- SCHEDULEREC QUERY END
12/04/2008 13:00:11 Next operation scheduled:
12/04/2008 13:00:11
------------------------------------------------------------
12/04/2008 13:00:11 Schedule Name:         EXCELLERA_ARCHIVE2
12/04/2008 13:00:11 Action:                Incremental
12/04/2008 13:00:11 Objects:               \\172.17.16.101\archive2\
<file://172.17.16.101/archive2/>
12/04/2008 13:00:11 Options:               -subdir=yes
12/04/2008 13:00:11 Server Window Start:   13:00:00 on 12/04/2008
12/04/2008 13:00:11
------------------------------------------------------------
12/04/2008 13:00:11
Executing scheduled command now.
12/04/2008 13:00:11 --- SCHEDULEREC OBJECT BEGIN EXCELLERA_ARCHIVE2
12/04/2008 13:00:00
12/04/2008 13:00:11 Incremental backup of volume
'\\172.17.16.101\archive2\'
12/04/2008 13:00:13 ANS1228E Sending of object
'\\172.17.16.101\archive2\*' failed
12/04/2008 13:00:13 ANS1063E The specified path is not a valid file
system or logical volume name.
12/04/2008 13:00:13 --- SCHEDULEREC STATUS BEGIN
12/04/2008 13:00:13 --- SCHEDULEREC OBJECT END EXCELLERA_ARCHIVE2
12/04/2008 13:00:00
12/04/2008 13:00:13 ANS1512E Scheduled event 'EXCELLERA_ARCHIVE2'
failed.  Return code = 12.
12/04/2008 13:00:13 Sending results for scheduled event
'EXCELLERA_ARCHIVE2'.
12/04/2008 13:00:13 Results sent to server for scheduled event
'EXCELLERA_ARCHIVE2'.


Best Regards,

John D. Schneider

This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the
use of the addressee(s) named above. If you are not the addressee, or the
person responsible for delivering this to the addressee(s), you are notified
that reading, copying or distributing this e-mail is prohibited. If you have
received this e-mail in error, please contact the sender immediately.