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.
When I download WebFOCUS reports in CSV format (PCHOLD FORMAT COMT), they often come with lots of NUL bytes in the content. I could not figure out what causes this. As a workaround I open those reports with Excel and save them in place. This somehow removes the NUL bytes while leaving the strings intact, so I can then use the CSV files for further processing. How can I prevent those NUL bytes in the first place?This message has been edited. Last edited by: Kathleen Butler,
Propagates missing values to a delimited HOLD file when the field has MISSING=ON in the Master File. The HOLD formats supported for SET NULL=ON are COM, COMT, TAB and TABT.
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
SET NULL = ON or OFF did not work for me, but I found another solution. Apparently the problem was related to the formatting used on some fields: ACTUAL=A9.
I suppose this could be fixed directly in the master files if one is able to edit them. I instead fixed it by defining new fields for my report and using those instead of the original ones, as in
DEFINE FILE SOMETABLE FIXED_FIELD/A9V = ORIGINAL_FIELD; END
The "V" in the formatting made the difference. No more NUL bytes in the output.