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.
How can I handle the scheduling of a report that should run every Monday morning as well as the the of the 1st of the month?
Actually I have 2 schedules: 1 for every Monday, another one for month start. But I anticipate 2 reports when the 1st of the month will a Monday.... What do I have to do to control this? Any exception parameters?
Need your help again, thanks.
quote:
This message has been edited. Last edited by: Marikaki,
Marikaki
WF 7.7.03m, MRE, BI Dashboard, DevStudio, Report Caster, Windows 7, I.E. 8/9, Apache Tomcat 6.0, Derby Output formats: Excel2K, PDF, HTML, AHTML
One method that I have employed over time is to have the run dates set in a calendar file with a final step in the caster job to read the date file for the next date and then reset the nextruntime value in BOTSCHED accordingly. This would obviously require a level of maintenance but may give you a greater flexability.
Another method is to use DM to calculate the BOW date and check to see if it is a Monday or the first of the month. If it is neither of these then set &KILLRPC to 'Y'. This would require that the job is run every day and might not be what you want. However, the overhead is small as the DM would be the very first part of the process to run and would be short most of the time.
Just two ideas of many that you might be given.
T
Edited for Speel chuckingThis message has been edited. Last edited by: Tony A,
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
We have a preprocessing fex that check for the correct day to run. If it is not, we set &&KILL_RPC (2 & not one) to Y and the job stops. Also, you have to use the pre-processing fex in every task in the job (at least we do in 7.1.3) which is a pain.
Hey now there's an idea. Use &KILL_RPC to kill a task and &&KILL_RPC to kill the job. Since && are globals, seems &&KILL_RPC could tell RC to flush the rest of the job and &KILL_RPC would flush the current task.
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
because I'm very busy these days I will get back to you as soon as I can. I've read the ideas and I don't understand very well I will need more detail in a while to execute. Thank you for understanding.
Marikaki
WF 7.7.03m, MRE, BI Dashboard, DevStudio, Report Caster, Windows 7, I.E. 8/9, Apache Tomcat 6.0, Derby Output formats: Excel2K, PDF, HTML, AHTML
The dumb way I have been using is to have 2 scheduled entries, one runs every Monday, and the other runs 1st of the month. That's because I not ready to do some killing yet.
Developer Studio 7.6.11 AS400 - V5R4 HTML,PDF,XLS
Posts: 305 | Location: Winnipeg,MB | Registered: May 12, 2008