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.
Has anyone else experienced this problem? Is this by default? As soon as a reportcaster task is added to a schedule it executes the added task immediately. I broke it down to the task's fex having "prompt for parameters" unchecked. If it is unchecked the fex runs as soon as I hit OK, if it is checked it does not.
The fex is a standard report sitting in MRE. The checked value is a working solution but the agony of having to undo the jobs that ran remains.
Yes, this is a known issue and there sis a work around to prevent this. I do however not know it exactly, so you might search on this site to find out how it should be done.
And please... update your signature, it will be helpful.
Frank
prod: WF 7.6.10 platform Windows, databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7 test: WF 7.6.10 on the same platform and databases,IE7
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006
Is it one you are just setting up? If you open it and change the schedule date/time it helps. I have opened a job to change it, unchecked the enable button, made changes closed it, then opened it and checked the enable and that seems to help.
Leah
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004
You've found one of those funny workarounds. It works, but for no apparent reason. The problem is that if the "prompt for parameters" is unchecked, you are unable to access the "parameters" tab inside of RC. So you have to go back and turn it back on.
The best solution is to set the begin time in the future. By default, when you create a new schedule the current date/time is added to the begin date/time. If the "Enabled" checkbox is checked on the first tab, then the fex runs immediately upon completing the schedule and saving. If the "Enabled" box is not checked, it will not run immediately.If the Begin Date/Time is in the future, the "Enabled" box has no effect and the job will never run as soon as it is saved. Buth then you have to modify this date/time if you ever go back and make changes. Yup - it's a hassle. And it's been around since the beginning of ReportCaster's days. Hopefully they can come up with a fix sometime.
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007