Because TSMBB is a DB2 cluster node.  DB2 knows nothing of volhist.out.  
Volhist will only be saved out where TSM is actively running, not on 
standby/backup nodes.

I'd recommend setting up shared or replicated disk where your volhist and 
devconfig, and maybe a copy of your DR plans can be saved to, though the DR 
Plan should still be sent somewhere offsite as well.

+----------------------------------------------------------------------
|This was sent by xaminmo AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------