Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Returncode\s+for\s+a\s+TDP\s+CMD\s+Script\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Returncode\s+for\s+a\s+TDP\s+CMD\s+Script\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] Returncode for a TDP CMD Script (score: 1): Author: Stefan Holzwarth <stefan.holzwarth AT ADAC DOT DE>; Date: Fri, 11 Sep 2009 10:01:05 +0200; Hi, we are using a Windows cmd Script for tdp Backups. At the TSM Server the schedule is defined as: tsm: TSMA>q sched tdp sql23full_SERVER33 f=d Policy Domain Name: TDP Schedule Name: SQL23FULL_SERV; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-09/msg00088.html (12,651 bytes)
2. Re: [ADSM-L] Returncode for a TDP CMD Script (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Fri, 11 Sep 2009 06:24:57 -0400; Without seeing your script, I suspect that the command that sets the return code might be running asynchronously rather than synchronously. I suggest going to the link in my sig and searching on: dia; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-09/msg00092.html (14,537 bytes)

Current List: 1 - 2
Page: [1]