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.
Instead of kicking off a Report Caster Schedule at a specified time, we want to kick off the job upon the completion of an event. For example, after a database has been updated, we want specific reports to get executed and distributed. Has anyone resolved how to trigger Report Caster jobs to run upon the completion of an exterior event?
Posts: 2 | Location: Modesto, CA | Registered: October 28, 2004
We don't have MRE here with ReportCaster so we can't use Event Handling. I was able to accomplish this using Dialogue Manager....
When the database is updated, a flag file gets written out...then I used Dialogue Manager to do the rest.
-* kick the job off at 8:00 am. in RC -SET &CNTR = 0; -RESTART2 -SET &CNTR = &CNTR + 1; SLEEP 60 -RUN -IF &CNTR GE 480 GOTO THEEND; -* kill the job after 8 hours! -* -* Note: zero is a good return code DOS STATE \\IMPRS01\APPS\PMS\DATA\HYFLAG.DAT -IF &RETCODE NE 0 GOTO NOFLAG; -* -* when flag is found, run your tasks or reports -* inline -SET &&PORTFOLIO = 'AAAAA'; EX PAREPORT -RUN -GOTO THEEND -RUN -* -NOFLAG -GOTO RESTART2 -RUN -* -THEEND
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003
There are a couple of manual ways to handle alerts in Self Service applications. The easiest way is to a have pre-execution procedure set the &&KILL_RPC flag. This flag is used to manually terminate a ReportCaster (or ETL Manager) job. Here is a simple pre-execution procedure:
TABLE FILE PROCESS_TABLE PRINT PROCESS_ID WHERE PROCESS_FLAG EQ 'Y' WHERE READLIMIT EQ 1 END -RUN -SET &KILL_RPC=IF &LINES GT 0 THEN 'N' ELSE 'Y';
This procedure simply queries a table and if any records are returned (LINES > 0), it sets KILL_RPC equal to 'N'. This will cause the job to run. If it is set to 'Y', the job will be cancelled.
The important thing to remember is you need to manually reset the alert condition before the ReportCaster job is rerun.