Which BOT tables hold information regarding currently running ReportCaster jobs? I found this: http://documentation.informati...htm?url=topic155.htm but I want to use the BOT tables to do the same.

- ABT

This message has been edited. Last edited by: Kerry,

If I understand the question, I think you are looking for BOTLOG, BOTLOG2 tables.

All BOT* tables are documented here:
http://documentation.informati.../source/topic134.htm

Scott,
Thanks for the reply, but BOTLOG appears to only hold details for finished/completed jobs, not those currently running. BOTLOG2 is the same, but with errors/messages for each.

I need to find out which jobs are currently running via the BOT tables or some other automatic/dynamic/programmatic method (i.e. not the ReportCaster console).

- ABT

ABT, did you ever find a resolution to this issue? I'm having the same issue. The BOTLOG record is written after the job is completed. There is a table called BOTSTATE, but I am unable to find any documentation on it.

quote:

ABT, did you ever find a resolution to this issue?

Unfortunately, no.

quote:

There is a table called BOTSTATE, but I am unable to find any documentation on it.

I can confirm that that doesn't seem to have anything to do with this issue. I have three ReportCaster jobs running and my BOTSTATE table is empty.

Seems the best you can do is see when 'NEXTRUNTIME' is and check the logs to see if there is a corresponding entry for that time.

Why do I always feel like I want to do things with WebFOCUS no one else wants to do...

- ABT

I wonder how the console knows?

\ibi\ReportCaster76\samples\C11_Get_Running?

Most likely via the Java API. More trouble than it's worth, at least for me...

- ABT

Correct, the ReportCaster Console uses the java api to get the status of jobs in the waiting queue and the running queue. Also, as stated above, BOTLOG AND BOTLOG2 only hold information for completed jobs since the records are written after a job finishes.

ABT, did you ever find a good solution for this?

I want to be able to grab the same information so that we can exit reports if the dependent schedules have not executed yet.

quote:

Originally posted by Joey Sandoval:
ABT, did you ever find a good solution for this?

Still no, but I kind of stopped looking/asking.

quote:

I want to be able to grab the same information so that we can exit reports if the dependent schedules have not executed yet.

I think you're going to have to roll your own. Something I was considering was this. Write out a start record and a stop record to a status table for all the jobs. In your dependent jobs, read this table in the first step, if the prior job has finished (i.e. a stop record is present), proceed. If not .... (here's where it gets tricky). I've considered rewriting the BOTSCHED table's NEXTRUNTIME field to 10 minutes in the future so it would (hopefully) reschedule. I've considered using the ReportCaster API to reschedule or re-execute the job. Do a DOS Sleep. Schedule it to run once an hour and quit when it reads the success message. Auto enable/disable the dependent job throughout the day and have one main job to reset the values at midnight. etc etc etc.

I know ReportCaster has Pre/Post processing steps, but I really need something more like DTS/SSIS for job scheduling.

- ABT