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.
I would strongly suggest comparing the contents of the hold files HOLDACCT, HOLDJOBS, HOLDMNTH and HOLDYEAR, from the run when it is first and when it is second.
1ST: HOLDACCT DISK 66 V D:\ibi\srv76\dm\edatemp\ts000079\holdacct.ftm 2ND: HOLDACCT DISK 25 V D:\ibi\srv76\dm\edatemp\ts000079\holdacct.ftm
I didn't check them all but the record lengths of these two are different between your two different posts of filedef results. You need to investigate why that is.
You might want to consider doing an APP HOLD to two different permanent locations, moving the 'bad' fex around so that you can look at and compare the contents of the files you are using to test against in your WHERE clauses. I am almost certain that is where the problem is.
I would try moving all of your hold file logic used to create the hold files for your WHERE clauses outside of the PDF OPEN / PDF CLOSE code stream. The fact that the report runs fine in second/last position when the WHERE clauses are removed makes me suspicious not of the HOLD files, but the MODIFY logic that creates them.
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007