We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Support for floating point "DECfloat" data types in DQM so floatingvalues not being rounded to a Double datatype in Cognos BI
Support for floating point "DECfloat" data types in DQM so floatingvalues not being rounded to a Double datatype *************************************************************
The IEEE Standard IEEE 754-2008 (previously called IEEE 754r) for binary floating-point arithmetic was revised to include the definition of decimal floating-point arithmetic. This replaced the prior standard IEEE-754-1985.
This is intended mainly to provide a robust reliable framework for financial applications that are often subject to legal requirements concerning rounding and precision of the results, because the binary floating-point arithmetic may introduce small but unacceptable errors.
Vendors such as IBM have implemented hardware level support to accelerate calculations as opposed to implementations in software (such as DECIMAL (N,M)) typically involve.
Support for such a 'DECfloat' type must take into consideration the following characteristics which a customer may assume IBM Cognos offers once support is claimed:
1) which vendor data types are treated as a 'DECfloat' type (separate stories should be added re DB2, Informix, Vertica, ... as appropriate) 2) what IBM Cognos has done to avoid automatically injecting expressions (i.e cast as double, * 1.E0 etc) that could cause a type conversion 3) how IBM Cognos allows a customer to control (Cognos instance, package or model) what rounding mode Cognos BI defaults to 4) if IBM Cognos detects what rounding mode the RDBMS may be configured what it does based on that fact (ignore, warn, ...) 5) if IBM Cognos supports SQL syntax extensions vendors may offer such as IS [NOT] INFINITE, IS [NOT] NAN, SNAN 6) how automatic div-by-zero avoidance in Cognos BI can/should be used when customer expects IEEE behaviour re 0 / 0, 1 / 0 7) if IBM Cognos supports quantize 8) how data is exported by IBM Cognos (save-as) or imported (personal data) where someone presumes support for DECfloat 9) ensure documentation is provided with respect to customers updating existing Cognos BI apps where those types may have been 'treated' as a DOUBLE PRECISION etc
See attached documents and associated reference links:
Do not place IBM confidential, company confidential, or personal information into any field.