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.
We have WF server installed on Mainframe and we recently upgraded from 7704 to 7708. After the upgrade we are having an issue printing Times New Roman font with bold or italic. We found one change between versions, NLSCTRL parameter in codepage, in 7704 default setting is OFF and 7708 default is ON. Does anyone know how to change NLSCTRL from ON to OFF? This parameter can't be changed on screen(no option in Webconsole nlscfg.err), manuals say run a TSGU command but not sure about the right command. Thank you!This message has been edited. Last edited by: FP Mod Chuck,
You should be able to right mouse click on nlscfg.err and choose edit. Then add NLSCTRL=OFF Click the Save button and say OK to restart the reporting server.
I don't have access to a mainframe server so I can't verify what I am telling you. I found these instructions in a mainframe case on techsupport.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005
Thank you for your reply. NLSCTRL is not there to edit. We only see parameters below CODE_PAGE(65002 Unicode(UTF-EBCDIC)) LANG(AMENGLISH) DATEOUTPUT(DEFAULT) COLLATION(CODEPAGE) and then under optional customization TSGU command(there is a text box to type the command and Run button) I think need to run a command but not sure.
If you can't type in the area where the other stuff is. Then I would try to put the NLSCTRL=OFF in the text box and the run button. If you aren't comfortable with that contact techsupport and I'm sure they can help you with this.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005
Thank you Chuck. We were able to change the NLSCTRL setting to OFF but that did not resolve the issue we are having with PDF outputs, it is still printing squares when the font is "Times New Roman" and bold or italic. If anyone experienced this issue before and have a solution please help. Thanks!
I haven't had this exact problem, but I took a quick scour of the server manual to see if I could find an answer for you.
Check out the commands for
PDFX {font-name} and KTBL {pdfy-name}
I have a feeling it might be just what you need.
Font topics can always be a little confusing. Since pdf fonts are embedded, they come from the server. It's the font's themself (are I and B missing?) Or, it's in that command to configure the font.
WebFocus 7x, 8x, Win / Linux, any output format
Posts: 70 | Location: reading, pa | Registered: April 07, 2007
jnc, Thank you for taking time to look into this issue. I also found this in the manual and we tried this in server console but returned an error(NLS configuration error). I have a case open with ibi for this issue, it's been several weeks now but haven't got a response back. Thanks again.
Chuck, Thanks for the reply. I did ask them to escalate the case but no answer at all. I started using IBI products about almost 20 years ago, it was the best customer service by then but not anymore.