The TSM central scheduler forces multiple scheduled events for the same node
to run one at at time. I know of two ways to get file-oriented backups and
database backups to run concurrently.

One approach is to set up a schedule with 'action=command' to run a script
that starts several background processes to run the incremental backup and
the various database backups.

The other approach is to associate several node names with the same client
system, each with its own client scheduler process, and run each of the
overlapping events under a different node name. It is probably easiest to
set up the multiple node names by creating multiple server stanzas in
dsm.sys, each with a different nodename and tcpclientport setting. You
would than start multiple instances of 'dsmc sched', each with a different
-servername option.
=========================================================================