Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*pre\s+and\s+post\s+sched\s+on\s+NT\s+TSM\s+5\.1\.1\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*pre\s+and\s+post\s+sched\s+on\s+NT\s+TSM\s+5\.1\.1\s*$/: 7 ]

Total 7 documents matching your query.

1. pre and post sched on NT TSM 5.1.1 (score: 1): Author: Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>; Date: Mon, 22 Jul 2002 15:48:55 -0400; We noticed after upgradeing the TSM client on NT that those servers with pre and post sched commands were not backing up. Anyone else experience this? DSM.OPT entries: preschedulecmd e:\adsmbackup\ci; /lists/html/ADSM-L/2002-07/msg00787.html (39,752 bytes)
2. Re: pre and post sched on NT TSM 5.1.1 (score: 1): Author: Andy Raibeck <storman AT US.IBM DOT COM>; Date: Mon, 22 Jul 2002 16:03:53 -0400; This is the correct behavior starting with the 5.1 client. Have you looked up message ANS1902E? It explains what you are seeing. Also, check out the client manual, chapter 7 "Automating Tasks", secti; /lists/html/ADSM-L/2002-07/msg00788.html (40,737 bytes)
3. Re: pre and post sched on NT TSM 5.1.1 (score: 1): Author: "Rushforth, Tim" <TRushfor AT CITY.WINNIPEG.MB DOT CA>; Date: Mon, 22 Jul 2002 16:35:40 -0500; The first error message below tells you what is happening - the pre command failed - the schedule is not executed. This is new with 5.11 - if the preschedulecmd fails, the schedule doesn't run. Tim R; /lists/html/ADSM-L/2002-07/msg00795.html (8,943 bytes)
4. Re: pre and post sched on NT TSM 5.1.1 (score: 1): Author: Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>; Date: Tue, 23 Jul 2002 11:10:34 -0400; Well, yes, the preschedcmd fails....That's the question. It did not fail under the previous release, and when run apart from the backup by running the script by ilself, then doing the backup without; /lists/html/ADSM-L/2002-07/msg00838.html (9,305 bytes)
5. Re: pre and post sched on NT TSM 5.1.1 (score: 1): Author: Andy Raibeck <storman AT US.IBM DOT COM>; Date: Tue, 23 Jul 2002 11:35:47 -0400; Unfortunately I don't think we can determine why your script is failing, at least not without more information. I don't believe that the change in TSM release is responsible for the script failure, a; /lists/html/ADSM-L/2002-07/msg00840.html (11,687 bytes)
6. Re: pre and post sched on NT TSM 5.1.1 (score: 1): Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>; Date: Tue, 23 Jul 2002 08:50:24 -0700; Try running the tsm scheduler service using the same logon that you use to run the commands manually and see if that works.; /lists/html/ADSM-L/2002-07/msg00844.html (8,809 bytes)
7. Re: pre and post sched on NT TSM 5.1.1 (score: 1): Author: "Rushforth, Tim" <TRushfor AT CITY.WINNIPEG.MB DOT CA>; Date: Tue, 23 Jul 2002 11:06:04 -0500; Sorry, your original question was that the servers were not backing up not why the preschedule command was failing. We always route the output of all commands in pre/post commands to a pre/post outpu; /lists/html/ADSM-L/2002-07/msg00846.html (9,040 bytes)

Current List: 1 - 7
Page: [1]