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.
This morning we had two reports error out, both have historically ran fine with no problems. On one report we recieved the error: DECIMAL OVERFLOW--FIELD SET TO MAXIMUM and a competely seperate second report error was THE FORMAT USED WITH FIXFORM IS INCOMPATIBLE WITH THE DATA FORMAT E05. Using different fields and tables with none in common.
This is where it gets odd, without making any changes to the FEX we were able to go in to ReportCaster and kick off the reports again and they ran with out any errors.
Has anyone had this issue before and were you able to figure it out? I'm stumped.
Could be but I highly doubt it. These were two distinct data sets pulling different information from different tables. It all happened very quickly this morning.
No idea about the first error but for the second error
quote:
THE FORMAT USED WITH FIXFORM IS INCOMPATIBLE WITH THE DATA FORMAT E05.
This sounds like the master describing the file for the fixform does not match the actual file itself. Someone may have added a new or updated master file with the same name as the one used in the fixform in the path of your master file descriptions. You may want to look in to that possibility.
Good luck
et
FOCUS 7.6 MVS PDF,HTML,EXCEL
Posts: 115 | Location: Chicago, IL | Registered: May 28, 2004
Reportcaster uses apppath set by report server. You can get different results if you are running different copies of master or focexecs locally. Sounds like that is what is happening. Check to see if any of the underlying .mas files your app is using hasn't changed locally, or for that matter, any called fex files
With that in mind, place APP SHOWPATH into your fex to confirm the list of APPs and in which order they are searched. Also include -SET &ECHO=ALL;. Turn procedure tracing on for the run and then look at the trace. Hopefully that may help you a bit.
Don't forget to turn tracing off again.
TThis message has been edited. Last edited by: Tony A,
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004