Sharon,

>Is there
>something different in the way the SQL Agent runs as compared to the
>regular ADSM Backup-Archive client???

Not in terms of how it binds objects to a management class


>Does the SQL Agent require that if
>the first entire server backup was done to tape that the remaining
>transaction logs are also required to go to tape?

No

>We want to be able to
>take the first full backup of the month offsite and keep the changes
>(i.e. the transaction logs) on disk.  What am I missing????

I would suggest you check the following:

1. Is the SQL agent using a management class that sends the backups
directly to tape?
    (Check the default management class for policy domain in which the node
is registered?)

2. Do you have a maxsize threshhold on the disk pool that is being
exceeded?  That is, are
     the incrementals large enough to bypass the disk pool?

3. Is there ample free space in the diskpool ?

Having said all that,  have you considered binding all log files to a
special management
class that sent them to a diskpool that didn't migrate?  thast would
require setting up a separate
pool for this purpose but could eliminate flipping migration threshholds...

Chris Zaremba
ADSM Agent Development
internet  zaremba AT us.ibm DOT com