Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] $ in fieldname

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] $ in fieldname
 Login/Join
 
Gold member
posted
Is there any way to force WF to accept a $ in an existing fieldname that was created from a mainframe table? Here's the line from the master file:

FIELDNAME=FCINSAMT$, ALIAS='FCINSAMT$', USAGE=P17.2, ACTUAL=P8, $

Thanks.

This message has been edited. Last edited by: Kerry,


PROD: WebFocus 7.6.9 on WinXP
 
Posts: 59 | Registered: October 31, 2006Report This Post
Expert
posted Hide Post
What do you mean "force WF to accept a $ in an existing fieldname" - are you getting an error?


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Gold member
posted Hide Post
Yes, I'm getting an parsing error when I try to use the table in the painter. It will let me manually code it, but the field is in tics and blue. In the master file, the field line is green right after the first $ sign. I was thinking that was the reason I was getting the parsing error.


PROD: WebFocus 7.6.9 on WinXP
 
Posts: 59 | Registered: October 31, 2006Report This Post
Expert
posted Hide Post
I would guess that you are correct in your assumptions as the dollar sign is a termination symbol in the WF world.

Check with tech support to be sure though.

T



In FOCUS
since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2  
WebFOCUS App Studio 8.2.06 standalone on Windows 10 
 
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004Report This Post
Expert
posted Hide Post
FIELDNAME=FCINSAMT$, ALIAS='FCINSAMT$', USAGE=P17.2, ACTUAL=P8, $


I wouldn't normally edit the Master, but as a workaround you could remove the $ from the field name, leave the ALIAS as is because that's the name in the DBMS. I think this should work.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Gold member
posted Hide Post
Thank you Francis. That worked.


PROD: WebFocus 7.6.9 on WinXP
 
Posts: 59 | Registered: October 31, 2006Report This Post
Expert
posted Hide Post
That wasn't a stab in the dark, after the Master is generated, you can change the name of the columns and even the format (as long as the usage vs actual restrictions are adhered to). I usually never make any changes to a generated Master, because, unless there are tight restrictions on who generates metadata, someone can easily wipe out the changes by regenerating the metadata.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Virtuoso
posted Hide Post
quote:
Originally posted by Francis Mariani:
...
FIELDNAME=FCINSAMT$, ALIAS='FCINSAMT$', USAGE=P17.2, ACTUAL=P8, $

...
I'm curious why the generated synonym has the alias value quoted, but not the (identical) fieldname.

Anyway, if you want to keep the fieldname intact, it appears you can just quote it -- from what you say, the parser did not mistake the remaining $ as EOR when you snipped off the first. -- Since the problem is with the Painter (not in execution on the Agent), Hold files inheriting the fieldname-ending-in-$ should not cause a problem.


- Jack Gross
WF through 8.1.05
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] $ in fieldname

Copyright © 1996-2020 Information Builders