9.14.1 Ponctual planification

With the ponctual planification method, you can manually create an exploitation day from a referential.

The rp command creates an exploitation day from a referential. The first parameter is the name of the referential to plan. The second parameter, which is optional, is the start time of the new day with the format `YYYY-MM-DD [hh:mm:ss]'. If this parameter is not specified, the start time is fixed to the next day at midnight. The third parameter is the name of the day to create. If this parameter is not specified, the name of the new day is composed of the referential name followed by the start time with the `YYYY-MM-DD' format.

You can call the ei command to know if a referential is currently used to create a new day : The `Ref To Plan' property shows the name of the referential which is currently used by the day creation process or `none' if no day creation process is running.

When the day creation process is terminated, you can call the xdl command to print the day list : the new day should appear in this list.

In our example, we will create a referential with two tasks. The first task will be executed every days and the second will never be executed. Then, we will create an exploitation day from this referential.

First, we create a referential `r1' with the ra. Then we add two tasks `t1' and `t2' with the xta command. We add an operation to the first task to execute it every days (rtoa add always) :

$ dio87c ra r1
$ dio87c rta r1 t1
$ dio87c rta r1 t2
$ dio87c rtoa r1 t1 add always

First, we create an exploitation by simply calling the rp with the referential name :

$ dio87c rp r1
New day name : r1_20050118
from referential : r1
start time : 2005-01-18 00:00:00
[...]
Termination

The name of the new day is `r1_20050118'. You can see that the start time of the new day is fixed to the next day at midnight. The tasks of this day will wait until midnight before to start. Until midnight, they are uninitialized :

$ dio87c -- xtl -s r1_20050118
t1      uninitialize

Then, we create a second exploitation day from our referential by fixing the start time of the new day :

$ dio87c rp r1 "2005-01-17" 
New day name : r1_20050117
from referential : r1
start time : 2005-01-17 00:00:00
[...]
Termination
$

The new day is `r1_20050117'. To check that the day is created, we print the day list with the xdl command, and we print the task list of the new day with the xtl command :

$ dio87c xdl
r1_20050117 
r1_20050118 
$ dio87c xtl r1_20050117 
t1
$

We can see that only the task `t1' was created in the day `r1_20050117'. This task was selected, because we added an operation to select it every days (`rtoa ... add always'). The task `t2' was not selected because it does not have an operation to select it.

Now, we print the task list with the `-s' option to print the state of each task :

$ dio87c -- xtl -s r1_20050117 
t1      terminated

You can notice that the task `t1' is terminated : the task starts as soon as the day is created !

If we want to modify tasks or jobs (to cancel or to disable them) before the exploitation day starts, we must use the `-d' option of the rp command : this option disables the day which is created, and no tasks or jobs can start when the day creation is terminated.

To verify this, we remove the day `r1_20050117' and we create a new day by using the `-d' option :

$ dio87c xdk r1_20050117 
$
$ dio87c -- rp -d r1 "2005-01-17" 
New day name : r1_20050117
from referential : r1
start time : 2005-01-17 00:00:00
[...]
Termination
$

We print the task list and we can see that the tasks are uninitialized :

$ dio87c -- xtl -s r1_20050117 
t1     unitialized
$

In fact, the day is not enabled. The xdi command shows that the `enabled' property of the day is set to `false' :

$ dio87c xdi r1_20050117 
Day Name:       r1_20050117
Start Time:     2005-01-17 00:00:00
Enabled:        false
Locked:         false
Referential:    r1
Auto Purged:    false
$

Now, you can modify the day to disable or to cancel job or task execution. To activate the day, we use the xdse command. We can see that the tasks are executed :

$ dio87c xdse r1_20050117 true
$
$ dio87c -- xtl -s r1_20050117
d1     terminated 
$

If the task is always uninitialized, it's probably because you create a day with a start time in the future ! In this case, you just have to wait until the start time, and the tasks will be executed. To know the start time of a day, you can use the xdi command :

$ dio87c xdi r1_20050117 
Day Name:       r1_20050117
Start Time:     2005-01-17 00:00:00
Enabled:        true
Locked:         false
Referential:    r1
Auto Purged:    false
$

There is a last point which can avoid a day to start : if the engine of the `dio87d' daemon is disabled ! To know if the engine is enabled, you must call the ei command :

$ dio87c ei
Enabled:	true
[...]
$

If the `enabled' property is set to `false', the engine is stopped, and no task can start. In this case, you must use the ese command to enable the engine.