[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

1784.0. "Problem with UNTIL used with EVERY in a AT clause" by RIVAGE::LAVILLAT () Fri Nov 08 1991 08:46

I have a small problem with Scheduling/Scoping behaviour :

Consider the following (suppose it is 10 am ) :

MCC> getevent os a t a any event , at every 24:00:00 until 15:00:00 , -
_MCC>  for start 12:00:00 dur 6:00:00
                             

Question : At what time this GETEVENT directive will end ?

I would say 15:00, but in fact it will end at 18:00.

Consider also :

MCC> getevent os a t a any event , at every 24:00:00 until 15:00:00 , -
_MCC>  for start 16:00 dur 2:00
                             

Question : At what time this GETEVENT directive will end ?

I would say it should never start since the start time of the scope is
after the until time of the schedule, but... 


What I realised in fact is that the UNTIL part of an AT clause has only a
meaning modulo the EVERY clause duration, since it is only evaluated once 
an EVERY time (here once a day).

So, 15:00:00 in my example may be in fact from 15:00 to 15:00 + 24:00.

My problem is that I am currently implementing such scheduling orders using
a repetition period of one week, and so if you say end Friday at 18:00, it
can end only the next Monday or Tuesday,... (bad luck for the week-end) !


I understand it may be a simplification choice to have the Information Manager
code simpler, but one could expect the IM to cancel the call to the Management
module once the end time/until time of the schedule part is reached ?

Should I consider that as a bug (so that I can expect this behaviour to be
changed some day) or is it only a feature ?

Regards.

Pierre.

T.R Title User Personal
Name Date Lines

1784.1 getevet uses FOR not AT TOOK::CALLANDER MCC = My Constant Companion Fri Jan 03 1992 11:33 16

T.R	Title	User	Personal Name	Date	Lines
1784.1	getevet uses FOR not AT	TOOK::CALLANDER	MCC = My Constant Companion	`Fri Jan 03 1992 11:33`	16
	well to start getevent uses FOR not AT. What you are asking for is that every 24 hours you want to go out and see if there is an event (which are instantaneous), and that you want to do this until 3:00 today. In long form what you entered equates to: at start = NOW every 24:00:00 until 15:00:00-today What you are really looking for (my guess) is something like at every 24:00, for duration=+9:00 every 24 hours look for all events fro a 9 hour period, or something to that effect. jill

    well to start getevent uses FOR not AT. What you are asking for
    is that every 24 hours you want to go out and see if there is
    an event (which are instantaneous), and that you want to do
    this until 3:00 today. In long form what you entered equates
    to:
    	at start = NOW every 24:00:00 until 15:00:00-today
    
    What you are really looking for (my guess) is something like
    
    	at every 24:00, for duration=+9:00
    
    every 24 hours look for all events fro a 9 hour period, or something
    to that effect.
    
    jill