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.
Hello, I have a customer who's creating a DFIX file to be used as an input to another system. Somehow this procedure used to not have any extra spaces in WF8009 but some fields show up as spaces instead for blank or empty in WF8201. He didn't want to change the procedure to add MISSING ON for the fields in question. The file is a comma separated data values and has some defines to insert blanks to skip to next field as below BLANK/A1 =''; The above field when held as PCHOLD FORMAT DFIX shows up as a SPACE. Any ideas on how to get rid of these extra spaces in the entire output file?
Thanks in advance!!This message has been edited. Last edited by: FP Mod Chuck,
DEFINE FILE CAR
BLANK/A1 = '';
END
TABLE FILE CAR
PRINT CAR BLANK COUNTRY BLANK SALES
ON TABLE PCHOLD FORMAT DFIX DELIMITER ,
END
We tried to suggest to use MISSING ON but, they're not looking to change lot of defines, they claim that this was working with no spaces/blanks in the output file from 8009 release but not in 8201. Is there a setting to squeeze or replace all spaces in the file?
Since Chuck is getting the same result in his 8009 release, I would suggest looking at your edasprof file from 8009 and see if there was a SET that didn't get included when upgrading to 8201M.
Hallway
Prod: 8202M1
Test: 8202M4
Repository:
OS:
Outputs:
Posts: 608 | Location: Salt Lake City, UT, USA | Registered: November 18, 2015
Both evnvironments look same we didn't find any other SET differences. It is odd though why its behaving this way. Also, I found if we use FORMAT COM, it will supress these blanks but, we end up with double quoted strings.
This sounds like MISSING/NULL vs. BLANK. We use comma and tab delimited files a lot (DFIX files). Blank fields are returned with delimiter blank delimiter. MISSING/NULL fields are two consecutive delimiters. You might check your metadata to make sure nothing changed.
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
Thanks, even with CAR example we're getting different outputs so thats still odd. There must be something environmental, its 8201M actually where I'm seeing these spaces/blanks.