As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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, 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.
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.
WebFOCUS All Releases
Posts: 45 | Location: NYC | Registered: September 21, 2007
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.