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.
-INCLUDE testrcst -RUN -IF &LINES EQ 0 GOTO ENDRPT; SET ASNAMES =ON TABLE FILE MYADD PRINT MY_ADD AS 'DEST' ON TABLE PCHOLD END
-ENDRPT SET ASNAMES =ON TABLE FILE MYADD PRINT MY_ADD AS 'DEST' ON TABLE PCHOLD END
I am getting an error; the number of character equal to the length of my email address are added infront of my email address making my email address invalid.
The leading character count is the same behavior we see in 7.1.3 with VARCHARS. We had to make the setting change in edasprof... ENGINE DB2 SET VARCHAR OFF
Don't know about your data source or WF version, but that is the same behavior we now see with VARCHARS unless we make the setting above.
Hope this helps,
Kevin
WF 7.6.10 / WIN-AIX
Posts: 141 | Location: Denver, CO | Registered: December 09, 2005
You are welcome...I should mention that that setting can be applied dynamically inside your focexecs and can be reversed in the focexecs as well. We made the choice to turn VARCHAR OFF globally (in edasprof)rather than retrofit all of our existing code. If we do run across the need for this new VARCHAR fuctionality, we know we will have to issue the ENGINE DB2 SET VARCHAR ON command on an individual focexec basis.
Glad it worked for you,
Kevin
WF 7.6.10 / WIN-AIX
Posts: 141 | Location: Denver, CO | Registered: December 09, 2005
If you set the VARCHAR stuff before you create the master files, then they will be built without the "V" on the USAGE and ACTUAL attributes. Otherwise, you can edit your masters and remove the "V"'s so you will not have to issue the VARCHAR setting anymore.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott