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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
Say there are 3 jobs that are to run in sequence and JOB2 runs only if JOB1 runs successfully and JOB3 runs only if JOB2 runs successfully. Now assumming you have worked out what "runs successfully" means, here is what I would do.
Set up JOB1, JOB2 and JOB3 in report caster and schedule JOB1 to run. When it "runs successfully", use DSTRUN to tell Report Caster to run JOB2. Likewise, when JOB2 finishes, use DSTRUN to tell Report Caster to run JOB3.
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
Suggestion from our ReportCaster technicals: &&KILL_RPC in a pre-execution fex is the way to go. Each task has its own set of pre/post-execution fexes. So for each task, have it run a pre-execution fex with &&KILL_RPC; depending on the condition/test that the pre-exec fex has to run, it could even be the same pre-exec fex for all of the tasks.
Kerry Zhan Focal Point Moderator Information Builders, Inc.
Posts: 1948 | Location: New York | Registered: November 16, 2004