What is the reason for Report Caster delay in running its scheduled job? The scheduled job is not even showing on the console on or after its scheduled time. However, it ran successfully after an hour of its scheduled time.

Any ideas/suggestions would be appreciated
Thanks

Hi Sophie,
It might be worth checking with the server that the clock time
is correct as we had a similar issue a few years back where they had reset
the mainframe clock for daylight saving time but not the WebFocus server
so it was an hour adrift.
It's a stab in the dark but is certainly worth a 2 minute check.

Paul

Report Caster (here) will only process three jobs at a time (able to be set in RC config), any others that get executed will sit in a queue in an order decided by their priority setting. If you have long running RC jobs then this queue may take time to service. Look at the report caster console / status screen to see the queue and it's contents.

T

Both Tony and Madasabear are making valid points

Another possibility is the your application server is configured for the wrong timezone.

And to add to the list of possibilities -- if there happened to be a server or network issue, RC may not have been able to reach an MRE repository or a WF server at the scheduled time so it may keep trying until a proper connection is made. May even be that the RC server was not up at the schedule time so its recovery mode ran the procedure an hour later when it was brought up.

(However, my bet would be on either the Time zone difference or daylight savings issue.)

I had the same issue when i was in 5.2.
had to change the clock time by hand.
Upgrade, you'll be happy

Thanks for all the suggestions.

The next question are..
How do we check Report Caster server time? and how do we adjust it?

Many thanks
Sophie

First port of call should be your Unix admin, He/she is the one who will have to change it anyway.

From a WebFOCUS Caster point of view if they are on the same machine
then from a WebFOCUS adhoc window !date will echo back the system date and time and also
tell you what time zone is being used.

If Caster is on a different machine and you have access to the Unix box simple type date.

If you do not have direct Unix logon then ask the admin.

Hi there is a great technic that explains how to convert Zulu time at the following link: http://www.informationbuilders...developers/zulu.html

Then you can build a update of the botsched and upate the NEXTRUNTIME to affect when the job will be run next.

Thanks for the information.

Our Unix machine time is corrected and our Report Caster is on the same machine. But the scheduling job is run an hour later than when it was scheduled.

Is there somewhere within Report Caster where we can check it's time and if it's incorrected, how do we adjust it?

Thanks

5.2 as i recall did not adjust for daylight savings time, but then i was on a wintell server.
7.n is perfect, so you'll enjoy the upgrade.

Hi,

The Report Caster must either have it's own time registered some where or obtained the time from some where for executing the scheduled jobs.

My question was how do we find out it's time in order to rectify it?

Our scheduled jobs are currently run an hour later.

Any ideas or suggestions is much appreciated
Thanks

sophie , caster runs on GMT.
if you read the article Barry pointed you to, you'll see.
That article was written in version 5.

Hi,

Sorry I must be not making myself clear here. I know how to check and changed Report Caster scheduled time for jobs.

Our issue is the scheduled report run an hour late because according to the Report Caster, it's (for example) 9am at the time instead of 10am (this happened after the daylight saving recently).

Therefore, my question is where do the Report Caster registered it's time to excecute the scheduled jobs?

I hope this make a bit clearer...

Thanks

When you look in the schedule, you see a specific time. But the time recorded in BOTSCHED for that schedule is relative to GMT at the time you first scheduled it. So if you first scheduled some recurring job to run at 9am in the summer, and another one to run at 9am in the winter they run one hour apart.

As BarryS has said, this is stored in "Zulu" time and you need to look at the article he referenced to see where this is.

Hi,

Here is a shot in the dark, At one point we had a java version that calculated daylight savings time wrong so we were off by an hour.

So may want to check the java version.