Is there a specific reason you have a separate scheduler service for the TDP
backups? You could schedule your TDP backups via the standard nodename for
the server and that service. This is a positive in a couple ways:

1. Only 1 scheduler service on the client
2. The backups are single-streamed since TSM will only run 1 schedule at a
time. Your filesystem backups won't interfer with the TDP backups.

Just schedule both backups through the same nodename. The TDP backups are an
ACTION=COMMAND schedule. The script file that gets executed on the client
runs the TDPEXCC.EXE. There is a DSM.OPT file specified for the TDP agent.
When the TDP backup starts it connects back up to TSM server under that
nodename. This TDP backup doesn't have anything to do with the nodename
specified in the scheduler service.

And since the TDP agents now participate in TSM version and each has their
own filespace names, you don't even need to have a separate nodename for TDP
backups. With include statements you can specify the management class so you
don't need a separate domain/nodename for that. Except for those TDP agents
that don't do versioning...like Oracle.

Bill Boyer
"Some days you are the bug, some days you are the windshield." - ??