We must be looking at different redbooks. I am looking at "Tivoli Data
Protection for Microsoft SQL Server Installation and User's Guide
Version 2 Release 2"

There are 274 pages in this redboot. The Scheduler is covered in
Appendix C on page 197+. The pages you are referring to discuss
automatic expiration (i.e. include/exclude statements).

The steps regarding starting a scheduler in a clustered environment
begin on page 203.

They say:

7. Start the Cluster Administrator.

8. Select the SQL Server Cluster Group and create a new
Resource to represent the TDP for SQL scheduler service
(File->New->Resource). For example:
Name: TSM TDPSQL Scheduler
Description: TSM TDPSQL Scheduler
Resource Type: Generic Service
Group: MARSSQL1
Dependencies: MARSSQL1 SQL Server 7.0
Service Name: TSM TDPSQL Scheduler
(this MUST match the name of the service
that you installed earlier)
Registry Replication: None
IMPORTANT! Do not set up Registry Replication at this time.
This action is performed in a later step.

9. In the Windows command prompt window, change to the TDP
for SQL installation directory.
cd /d d:\Program Files\Tivoli\TSM\TDPSql

10. Enter a command that connects with the TSM server. Specify
the /tsmpassword=tsmpasswordname parameter to ensure the
correct password is stored in the registry. This allows the
scheduler service to properly connect automatically to the TSM
server.
tdpsqlc back model full /tsmp=marspswd /sqlserver=marssql1
Note: In the clustered environment, there must be a
CLUSTERNODE YES statement in the current TSM
options file.

11. From the Cluster Administrator, select the new resource and
bring it online (File-> Bring Online).

12. Select the new resource and modify its properties (File->
Properties). Under the Registry Replication tab, add a new
entry for the TDP for SQL nodename password registry entry.
For example:
SOFTWARE\IBM\TSM\CurrentVersion\BackupClient\NODES\<nodename>
Replace <nodename> with your TDP for SQL node name. For
example:

SOFTWARE\IBM\TSM\CurrentVersion\BackupClient\NODES\MARS
13. From the Cluster Administrator, select the new resource and
take it offline (File->Take Offline). This stores the encrypted
password in the quorum device so that a failover will pick up
the correct registry entries.

14. From the Cluster Administrator, select the new resource and
bring it online again (File->Bring Online).
Your system is now ready to run automatic daily full backups of the
SQL databases.