That was true with older TSM versions, but if your cmd file is written properly to do its own error checking and exit with a non-zero return code on an error, then the schedule should show as failed. I remember when this first started working (some time in version 5?). I have customers who run the TDP for SAP Oracle who do redo log backups every 2 hours or so and when there are no redo logs to backup, the brarchive script actually exits with a return code of 4 or something like that causing those schedules to suddenly start showing up as failed (erroneously in my mind, just because there are no redo logs to process shouldn't mean the command fails). Previously, all the cmd schedules would always show success because it successfully launched the cmd file. Now it should wait and get a return code back from the cmd script. Now, you will have problems if your original cmd script launches or calls other cmd scripts as those subscript return codes don't get passed back up the chain again. I believe the TDP for Domino or one of the TDPs example scripts are configured like that where they call subscripts. Perhaps that is something that affects your environment. It is very important that your original cmd file exit with a non-zero return code upon an error, which normally means you have to check the return code after every command within the script.
______________________________ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com "Ochs, Duane" <[EMAIL PROTECTED] M> To Sent by: "ADSM: [email protected] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: TDP for mail exch question ! 12/28/2005 01:16 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Steve, Yes but not at the TSM server "q schedule" or the operational reporting. The schedule launches the cmd file. To TSM the schedule is then successful even though the backup is still running. We wrote our own reporting scripts that verify completion based on the TDP client log files. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schaub, Steve Sent: Wednesday, December 28, 2005 12:33 PM To: [email protected] Subject: Re: TDP for mail exch question ! Duane, I don't understand your reference to not getting accurate schedule based success or failure messages - we use the batch method, and as long as the errorlevel from the command line backup is captured and used as the exit code, you should see accurate returncode results. Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ochs, Duane Sent: Wednesday, December 28, 2005 8:56 AM To: [email protected] Subject: Re: [ADSM-L] TDP for mail exch question ! Goran, There are many ways to perform it. I use a cmd file that is launched by TSM schedule and TSM scheduler service. The only issue is you don't get accurate schedule based success or failure messages. I know some others use windows scheduler to perform the task via a cmd file or bat file. There are also other products out there that allow scheduling with some reporting logic, I don't use any, but I have seen references on the adsm website. Duane -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of goc Sent: Wednesday, December 28, 2005 7:40 AM To: [email protected] Subject: TDP for mail exch question ! Importance: High hi all, urgent :-) how to automate exchange backup via TDP ? is it enough to write an *.bat or *.cmd with commands ? or is there a way to do it via tsm central scheduler assuming that dsmcad is running on exchange server ? sorry for maybe stupid question but im a unix-tsm admin and my windows guys are looking at me rather funny :-) thanks for any idea goran vipnet tsm 5.3.1.5 on AIX several times Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
