As has been said, you need to have a quiesced ADSM to use a mainframe backup
system.  The technique that we would use is to bring down ADSM, use FDRABR
application backup, and bring ADSM back up.  Yeah, it takes an outage, but
if you want the simplest, surefire technique,, that's one of them.

The timeing as far as offloading your DASD backuppool to cart is also
important.  If you have "drained" the DASD pool to cart, then you don't need
to worry about backing that up, also.

You notice above that I said that we "would" use that process.  We use the
risky approach of the "theory".
1) When backups are complete to the DASD backuppool we;
2) write our data to our "disaster recovery" pool and;
3  offload the data from DASD to cart
4) at a psuedo-quuiesced time, run the backup of all the "support" dsn's
based on the catalog filter name

Of course the theory is that this is a soft backup, but we have been
successful with our disaster recovery tests,,,so,,,,,,,,,(the DASD gods were
with us???)  I agree it's not perfect, but,,,,,