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.
For the WebFOCUS/FOCUS language to support parallel processing, IBI would have to add languane extensions to Dialogue Manager. You would have to be able to identify sections of code that are independent of each other and identify WAIT places. For example, I have a large program that collects data from more than 100 tables in our Oracle database and creates an XFOCUS database that is used for reporting.
Step 1 creates file and loads the population. Step 2 collects data and updates. Step 3 collects data and updates. Step 4 collects data and updates. .... Step 30 collects data and updates
This is a weekly batch job that runs around 3am and takes about 45 minutes to run, however, Steps 2-30 could run in parallel because they do not add to the population.
Since this program originated back in the dark times (before WebFOCUS), if I was going to do this program now and use parallel processing, I would write 30 distinct programs. After the population is created in step 1, I would use 29 DSTRUN calls in fex 1 to run the last 29 fexes. DSTRUN tells Report Caster to run a job now, so all 29 jobs would fire at the same time. I don't know that I would gain a lot, but it would be interesting to see how that would work.
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
There are ways to load-balance across multiple reporting services, each of which can be started on separate processors. It can be done, though it's not a transparent thing that magically happens. A good SE can get you set up to work across multiple processors.
I'll be honest -- short of heavy processing on FOCUS data files or some really hairy cross-DBMS joins the processing time on the Reporting Server (or WF Client for that matter) shouldn't be all that significant. Unless you're in a pretty complex environment multi-processing will only be an issue for the underlying DBMS. Your conversion to a multi-processor configuration may introduce more processing time than it reduces.
I'd wait until the problem presents itself before worrying about it. I'm on a four processor system and the tscoms are pulling very little juice. It's all in SQL Server.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007