Error messages for clearly incorrect include-exclude rules etc.

I've often noticed our users having trouble with exclude rules and I was wondering if you could put in some basic error reporting. Errors reported on-screen as soon as the TSM GUI is run would be ideal, as already happens with the message "ANS1036S The option '...' or the value supplied for it is not valid" when someone puts a dud line into dsm.sys/dsm.opt . If not, then error reporting logged in dsmerror.log would still be appreciated.

For instance, it seems that an exclude.dir or exclude.fs that ends in a slash always wrong, but users are often putting those slashes in when they manually edit the configuration file. So e.g. exclude.dir C:\test\ just gets ignored. Surely this can be flagged up by TSM as an error? We often find that users are backing up data that they meant to exclude because TSM tacitly ignores such erroneous exclude rules.

If it could detect when a user has put an exclude.fs where there should be an exclude.dir, or vice versa, then that would be good too. Recently a Linux user put an exclude.dir on a directory that had been set as a virtual mountpoint. He needed exclude.fs - TSM didn't tell him so, though.

On a related note, a rather adventurous user recently set up virtualmountpoint lines with a slash on the end of the line (e.g. virtualmountpoint /data/) and that made the client try to send all the data to us twice. Again, I would think that further checking of dsm.sys for obvious mistakes such as trailing back- and forward-slashes would prevent such misconfiguration.