There is no way to modify TSM behavior as you describe. In fact, your statement about excluding the files is exactly one of the reasons why TSM behaves as it does: so you can evaluate the reasons for the missed files, and take the necessary actions. We feel that it is better to flag the backup with an RC 4 and let you decide that you don't need backups for the particular files, than to flag the backup with an RC 0, only to discover after it is too late that you really needed the backups (in which case, you'd probably be asking why TSM didn't warn you that it couldn't back up the files).
Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Andy Carlson <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 06/26/2003 13:08 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: DSMC Exit Code Question I had an intersting question posed to me today and I don't have an answer. This person is checking the return code on the dsmc command to determine if the backup needs to be looked at or not. What he is coming across is files that are in the directory when the directory is scanned, but gone when the backup tries to back the file up. We did figure out we could probably exclude the files, but what we would like is for TSM not to give a non-zero return code what a file is not found. Thanks for any input into this matter. Andy Carlson |\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`' -. ;-;;,_ BJC Health Care |,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html