Zoltan, For TSM ACTION=COMMAND schedules, the return code of the last executing program within the script will be the error code that gets bubbled back up to the scheduler and recorded in the scheduler log. Make sure your scripts are trapping that error code and return that code, if there are other things in the script. Also... if you use the Windows START command, that won't work to trap the error code.
To find out what is causing the errors you are seeing, I recommend looking at the redirected output from the running command (if you are not redirecting the output from the command, you should do so) Also, the domdsm.log file should have recorded the errors it encountered. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 11/02/2006 11:32:40 AM: > These are all Domino TDP backups. They are a simple, one-line DOMDSMC > command-file/script. No post/pre anything. Just Domino voodoo. > > Nothing has changed on these systems, for a while. Some days the backups > run fine, other days they fail. >
