Hi Juraj, I know that you know how schedules work - I've seen your replies on the list - always accurate - not a problem in that area - it was not aimed specifically at you - it was more taking into consideration how TSM works - nothing to do with lingusitics - I assumed that a person who works with TSM would have noticed that the schedule actually did not kick off at all or that it kicked off later than expected(which I assumed was what Mike observed).
But it is also like they say - Assumption is the mother of all ......... Cheers Christo ====================================================== Hi christo, I know very well about how schedules work :-) I asked you a linguistic question. I try to be more precise: My understanding of Mike�s sentences per se is: The schedules did not run untill 02:41. The schedules may have run later, but Mike is either not sure about or not exact at this point. Your understanding is: the schedules did run at 02:41. Is this fully clear from Mike�s sentences? Or is this a conclusion from the sentence as written PLUS your assumption based on your general TSM knowledge, while the english sentence alone, without using TSM knowledge to transform syntax into semantics would result into my version? :) Juraj -----Urspr�ngliche Nachricht----- Von: Lawrence Clark [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 10. M�rz 2004 15:49 An: [EMAIL PROTECTED] Betreff: Re: AW: TSM Scheduling Hi Juraj, The backups will attempt to start anytime in the time set for duration. So if you have your backups scheduled to start at 1AM, and a duration of 2 hours, the backups could start as late as 3AM. They don't have to complete within the time of duration, just start. >>> [EMAIL PROTECTED] 03/10/2004 9:26:42 AM >>> Hi christo, this is question to improve my english: > My backups are scheduled to start at 01:00, but didn't start till 02:41 > Monday & 01:21 today. Any idea why? Does it tell the schedule did run at 02:41 for sure or is this only a probable explanation? regards Juraj -----Urspr�ngliche Nachricht----- Von: Christo Heuer [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 10. M�rz 2004 10:45 An: [EMAIL PROTECTED] Betreff: Re: TSM Scheduling Simple answer - the fact that the schedule actually ran means there IS an association - the fact that it does not run at the set time has to do with the schedule randomization % that is set on the TSM server and the length of the start-up window for the schedule for this client. Simple example: Schedule randomization=25% Length of start-up window is 1 hour. Client schedule is set at 01:00. The randomization will cause the schedule to physically kick off anywhere between 01:00 and 01:15. (25% of hour). Hope this explains it. Cheers Christo ========================================================== If it happens to me I know I have forgotten again to define an association. Check with Q EVE whether you really have your schedules scheduled. If not, search after an error in your schedule /associations definitions. If yes, search after an error in Q ACTL and in dsmsched.log,dsmerror.log on your clients - assuming your client tsm schedulres are running at all :-) regards Juraj -----Urspr�ngliche Nachricht----- Von: VANDEMAN, MIKE (SBCSI) [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 10. M�rz 2004 02:31 An: [EMAIL PROTECTED] Betreff: TSM Scheduling My backups are scheduled to start at 01:00, but didn't start till 02:41 Monday & 01:21 today. Any idea why? Mike Vandeman 510-784-3172 UNIX SSS > (888) 226-8649 - SSS Helpdesk > > ______________________________________________ E-mail Disclaimer and Company Information http://www.absa.co.za/ABSA/EMail_Disclaimer ______________________________________________ E-mail Disclaimer and Company Information http://www.absa.co.za/ABSA/EMail_Disclaimer
