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.
Ah I haven't seen the java exception error in a long time. We used to get them before our production went to 5.3.6. Report Caster does not parse the same as MRE, I've been told. Some times all you have to do is make a minor change to the code such as inserting a space in the heading at it runs fine. Check to see if you are 'following the rules' of the code. Consider semi-colons on your where statements and so on.
Good luck.
Leah
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004
I found the solution. The naming conventions userd for Focus Batch ZOS Mainframe files are less restrictive than the naming conventions for mainframe files used in WebFocus.