how to update next scheduled job

[Fábio Carvalho]

Hi, 

i recently did a massive  update on schedule timezone,using multicomand script and sdmsh. 

But to take effect it takes 1,2 executions (to execute on scheduled time). 

if i make any modification in schedule via WEB the next schedule update automatically and jobs runs on new scheduled time.

the script looks like this.

begin multicommand;

alter schedule root.s504333.'REGULAR' with time zone = 'Chile/Continental';

alter schedule root.s1591902.'VIERNES' with time zone = 'Chile/Continental';

alter schedule root.s1854225.'DIARIO' with time zone = 'Chile/Continental';

alter schedule root.s1659056.'DIARIO' with time zone = 'Chile/Continental';

alter schedule root.s1086610.'DIARIO' with time zone = 'Chile/Continental';

alter schedule root.s1663896.'DIARIO' with time zone = 'Chile/Continental';

alter schedule root.s1645293.'DIARIO' with time zone = 'Chile/Continental';

alter schedule root.s96297.'SEMANA' with time zone = 'Chile/Continental';

alter schedule root.s346978.'DIARIO' with time zone = 'Chile/Continental';

end multicommand;

and i executed as:

sdmsh --host localhost --port 2506 --user SYSTEM --pass ....<script-timezone.txt

Thanks

Fábio

[Dieter Stubler]

Hi Fabio,

Which version of schedulix (2.x) do you use ?
Can you please post a screenshot or detailed description of your schedule ?

Regards
Dieter

[Fábio Carvalho]

Hi Dieter,

I am using schedulix 2.7. Attached the examples:

Example 1: The job is scheduled to run at 08:00 am, but last time it ran at 09:00, the next schedule is correct. After few executions, jobs started run at correct time. Almost all jobs are doing the same.

Example 2:

   screenshot 1: Job's last run was at 21:00, next run 22:00. Correct time 21:00

   schreenshot 2: Just changed the name, the last run is "null" and next schedule is correct.

Additional information: Here in Chile we started daylight saving time last saturday (7/9). The previus Time Zone was GMT+4.

Thank you

Fábio

[Fábio Carvalho]

Hi, 

Just another example. Last ran was at 10:00am (wrong time - before change time zone / after starting daylight saving), next run wrong time also.

Thanks

[Dieter Stubler]

Hi Fabio,

The Probloem is that you only change the time zone for the root schedule of those jobs.
Every subschedule has its own schedule object which has to set to the correct time zone too.

You examples only use one subschedule called 'DEFAULT'.

To change the time zone for a master schedule and its subscedule do the following:

alter schedule root.'S0'.'REGULAR' (SYSTEM.'FOLDER_1'.'FOLDER_1_2'.'JOB_NAME') with time zone = 'Chile/Continental';

alter schedule root.'S0'.'REGULAR'.'S01_DEFAULT' (SYSTEM.'FOLDER_1'.'FOLDER_1_2'.'JOB_NAME') with time zone = 'Chile/Continental';

If you have more subschedules you add an alter for each additional subschedule like::

alter schedule root.'S0'.'REGULAR'.'S02_SECOND_SUBSCHEDULE' (SYSTEM.'FOLDER_1'.'FOLDER_1_2'.'JOB_NAME') with time zone = 'Chile/Continental';

Using the '(<full pathname of job or batch>)' clause you can just replace the 'S<jobid>' by 'S0' which makes it easier to use.
schedulix will replace the 'S0' with 'S<jobid>' before running the statement.

Please let me know whether this solved your problem.

Release 2.7 is a bit out of date. You should consider to upgrade to 2.9.

Regards
Dieter

[Fábio Carvalho]

Thanks Dieter,

I am out of office right now, being back  i will try and let you know.

About upgrade to schedulix 2.9, there is a way to upgrade without reinstalling zope?

Thanks

Fábio

[Dieter Stubler]

Hallo Fabio,

no Zope upgrade needed for upgrading to 2.9

Regards

Dieter

[Fábio Carvalho]

Thanks Dieter, 

worked fine the solution.

Fábio