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.
Issue: All of our reports run in MRE or from EDASERVE application folders but lately there are show-stoppers that preclude running the reports in report caster. This question has probably been raised before and my issue is likely how to search the sources.
We have found that some of these fixes resolve the issues: 1. Remove –EXITs. 2. Change SET EMPTYREPORT ON to SET EMPTYREPORT ANSI. 3. Place single quotes around amper variables – sometimes helps. 4. Avoid using global date variables, e.g. &&EO1Y 5. Use –SET &ECHO = ‘OFF’;
• If you have links that discussed the issue previously please respond with them. • If you have a search string that helped isolate the issue in either Focal Point or using ECL Search please send those suggestions as well.
Thanks so many times over in advance. The FOCUS Nation rocks. All the best for 2014 and Summit in Orlando
Sandy KadishThis message has been edited. Last edited by: S.J. Kadish,
2 things that burnt me. See if you have any of these.
1. Do you have any MORE in programs? Report Caster does not like MORE. 2. Names of Program. Procedure that I scheduled had more then 80 characters in name.
I suspect the MORE and COMPOUND issues are related.
An RC agent captures the first "formatted" output, and diverts it to RC's distribution facility; the rest of the fex is effectively flushed.
Since a compound request encompasses a series of TABLE requests, each nominally producing a "distributable" result, perhaps the music stops after the first such, and the compound facility (of either syntactic genre) never get the chance to package the outputs.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
Before you abandon ship on MORE, I suggest you check whether RC's allergy to it applies just to the formatted output step, or also to a HOLD step. (The answer may well be release dependent.)
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
MORE shouldn't be a problem. do you have a job log? that's what we want to look at to see where the error is. If there's an ECHO ON or ALL anywhere, you may well exceed MAXCOMMANDS. If its a name length, and if in fact that is the issue, then have your caster job be some_container.fex, where some_container.fex is -* this is some_container -INCLUDE app/myreallylongnamedmonster.fex -* but we really need to see the caster log. also, RC runs the edasprof, so any && vars that you set in there , you'll have access to. However some &vars get passed in various config files, that the mre java app runs, and caster doesn't have access to. so, again, we gotta see the log.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
We turned &ECHOes (plural?) off, which we usually do anyway for production jobs. The full RC log shows no errors but the only output is the cover letter.
If it's a matter of having &vars (global or not) set in a fex being used as a site profile by the WF client, you can get around it. We had to do so, and we're on 7.7.03 as well.
* On the reporting server, configure a new data service * When you configure your new service, type appname/fexname.fex in the profile field * You'll then configure caster to use that service... * go to ReportCaster Administration * Go to the Data Servers section * Edit the JDBC url listed here. We changed ours to simply add ;CLASS=CLIENT(dataservicename) to the end