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     Generating Masters with columns defined as D19.2 instead of P19.2

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Generating Masters with columns defined as D19.2 instead of P19.2
 Login/Join
 
Francis Mariani
Expert
posted
We have DB2 tables with numeric columns defined as Type=DECIMAL, Length=17, Scale=2. When we generate masters for these tables, the column is defined as P19.2. I would like them to be defined as D19.2.

Is there a server setting to change the behaviour of master file generation?

I do not want to manually modify the masters.

Thanks.


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
Kerry
Expert
posted Hide Post
Hi Francis,

Has this issue been resolved? The following topic from Information Builders' online document may be of interest:

Summary: HOLD FORMAT DB2 conversion of Decimal fields
http://techsupport.informationbuilders.com/known_problems/73601010.html

Hope this helps.

Cheers, Smiler

Kerry


Kerry Zhan
Focal Point Moderator
Information Builders, Inc.
 
Posts: 1948 | Location: New York | Registered: November 16, 2004Report This Post
susannah
Expert
posted Hide Post
fyi, same thing happens to us when i use AUTOSQL on the AS400 to gen masters for DB2 files.



In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Francis Mariani
Expert
posted Hide Post
Kerry, the issue described in the tech support document you provided does not apply exactly to my case.

I would like to have the DB2 decimal columns generated as D99.99 instead of P99.99 as they are now.

Thank you,

Francis.


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
<JG>
posted
For DB2 WebFocus generates Decimal as Packed to be able to support up to 31 positions.
WebFocus generates DB2 float as D format, which can go to D20.0 however subroutines/user functions only supoport D fields up to 16 digits (FTOA).
There is no server setting that can change this behaviour.

If it's simply an output issue because you want comma delimited output you can always specify that in the request ie COLUMN/P20.2C

JG
 
Report This Post
jimster06
Guru
posted Hide Post
Francis-
I would be concerned with the potential for loss of precision when converting from packed decimal to floating point.
I'm curious as to what the benefit is in this instance.


jimster06
DevStu WF 7.6.11
W7
HTML, PDF, EXL2K
 
Posts: 252 | Location: USA | Registered: April 15, 2003Report This Post
Kerry
Expert
posted Hide Post
Hi Francis,

Here is the info I received from one of our consultants.

Are you creating HOLD files? Or, are you using create synonym and not seeing the correct formats? If it is the latter, then the following setting should help:

ENGINE [DB2] SET CONVERSION format [PRECISION pp [ss]]


format

Is any valid format supported by the data source. Possible values are:

INTEGER

Indicates that the command applies only to INTEGER.

DECIMAL

Indicates that the command applies only to DECIMAL columns.

REAL

Indicates that the command applies only to single precision floating point columns.

FLOAT

Indicates that the command applies only to double precision floating point columns.

For this scenario:

ENGINE DB2 SET CONVERSION DECIMAL PRECISION 19 2

If hold files are a problem, then it will be something different.

Hope this helps. Big Grin

Cheers,

Kerry


Kerry Zhan
Focal Point Moderator
Information Builders, Inc.
 
Posts: 1948 | Location: New York | Registered: November 16, 2004Report This Post
<JG>
posted
The problem that Francis is having is not with the precision but with the USAGE format that is generated.

There is no way to control that in the metadata except by a manual change.

JG
 
Report 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     Generating Masters with columns defined as D19.2 instead of P19.2

Copyright © 1996-2020 Information Builders