IDS Forum

Re: Informix job scheduler issues

Posted By: John Miller iii
Date: Thursday, 26 January 2012, at 11:35 a.m.

In Response To: Re: Informix job scheduler issues (MARK COLLINS)

If you would like it to run every hour, then set the stop and start
time both to NULL and the tk_frequency to 1 hour. There are
several built in tasks with both the start and stop times set to
NULL (see mon_profile as an example)

John F. Miller III
STSM, Embedability Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
(Embedded image moved to file: pic65069.gif)

ids-bounces@iiug.org wrote on 01/26/2012 08:18:30 AM:

> From: "MARK COLLINS" <markc@myfastmail.com>
> To: ids@iiug.org
> Date: 01/26/2012 08:20 AM
> Subject: Re: Informix job scheduler issues [26051]
> Sent by: ids-bounces@iiug.org
>
> Fernando, John,
>
> Thanks for the responses. I found that the task was not actually
executing
> when I ran it with the name of the function. It never responded after
that,
> and I had to kill the session.
>
> Also, I was able to change the database (it's a test database) to a
logged
> database. Once I did that, I had to reset tk_next_execution, and then it
ran
> correctly, and ran successfully every hour until midnight. Then it
stopped,
> even though there was no "stop time" specified, and tk_next execution now

> shows 01/26/2012 13:15:00, which matches the start time I specified
> yesterday.
> I will watch to see if it really restarts then.
>
> I really wanted it to run every hour, period. Perhaps if I give a start
time
> of 00:10:00 and an end time of 23:55:00 it will work. Something else to
try.
>
> >> What is really happening:
> >>
> >> What happens when you create a task? The tk_next_execution time
> >> gets sent to CURRENT and time values are sanity checked. If the time
> >> values fit executing the task now we continue to execute the task else

> >> we do not execute the task, but just request that the task be schedule
for
> >> the
> >> next valid execution. This is tracked as the task running even though
the
> >> function
> >> itself was not executed, it was work done to manage this task (often
very
> >> small).
> >>
> >> In order to simulate the a task being executed by the scheduler
> >> the function exetask() are availible. These force the worker
> >> thread to execute the task now, even if the schedule indicates
> >> it should not be run.
> >>
> >> execute function exectask( tk_name )
> >>
> >> OR
> >> execute function exectask( tk_id )
> >>
> >> Something that does not seem correct is
> >> that the exectask() function does not take
> >> the function to be executed, but rather the
> >> name of the task which is is stored in tk_name
> >> column. In version 11.50 if you called this with
> >> an incorrect name to many times this could
> >> serverly slow down the scheduler and a restart
> >> of the scheduler would clena this up.
> >>
> >> I would look at the onstat option onstat -g dbc to view any error
> >> messages which occur during the running of your task.
> >>
> >> John F. Miller III
> >> STSM, Embedability Architect
> >> miller3@us.ibm.com
> >> 503-578-5645
> >> IBM Informix Dynamic Server (IDS)
> >> (Embedded image moved to file: pic00070.gif)
>
>
>
*******************************************************************************

> Forum Note: Use "Reply" to post a response in the discussion forum.
>

Messages In This Thread

• Informix job scheduler issues
  MARK COLLINS -- Tuesday, 24 January 2012, at 1:25 p.m.
  • Re: Informix job scheduler issues
    Fernando Nunes -- Tuesday, 24 January 2012, at 1:44 p.m.
    • Re: Informix job scheduler issues
      MARK COLLINS -- Tuesday, 24 January 2012, at 3:26 p.m.
      • RE: Informix job scheduler issues
        Bruce Simms -- Tuesday, 24 January 2012, at 3:32 p.m.
        • RE: Informix job scheduler issues
          John Miller iii -- Tuesday, 24 January 2012, at 3:58 p.m.
      • Re: Informix job scheduler issues
        Fernando Nunes -- Tuesday, 24 January 2012, at 5:35 p.m.
      • Re: Informix job scheduler issues
        John Miller iii -- Tuesday, 24 January 2012, at 7:21 p.m.
        • Re: Informix job scheduler issues
          MARK COLLINS -- Thursday, 26 January 2012, at 11:18 a.m.
          • Re: Informix job scheduler issues
            John Miller iii -- Thursday, 26 January 2012, at 11:35 a.m.
            • Re: Informix job scheduler issues
              MARK COLLINS -- Friday, 27 January 2012, at 10:34 a.m.
              • Re: Informix job scheduler issues
                Art Kagel -- Friday, 27 January 2012, at 10:44 a.m.
                • Re: Informix job scheduler issues
                  MARK COLLINS -- Friday, 27 January 2012, at 2:32 p.m.
                • Re: Informix job scheduler issues
                  MARK COLLINS -- Monday, 30 January 2012, at 5:25 p.m.
                  • Re: Informix job scheduler issues
                    Art Kagel -- Monday, 30 January 2012, at 5:39 p.m.
                    • Re: Informix job scheduler issues
                      MARK COLLINS -- Monday, 30 January 2012, at 6:35 p.m.
                    • (repost)Re: Informix job scheduler issues
                      MARK COLLINS -- Wednesday, 1 February 2012, at 4:51 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.