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.
Load source columns with data type REAL into data type DOUBLE
Introduce a new knob in the IDAA configuration console (that you open with TSO TELNET 1600): "Load source columns with data type REAL into data type DOUBLE"
When adding a table that has columns with data type REAL (float(4)) IDAA maps these columns to type DOUBLE on Netezza back-end. During IDAA load the values are converted from single precision floating point to double-precision floating point.
CDC mapping (replication) creates a mapping from the source REAL to the target float when enabling replication - the CDC apply engine insert implicitly converts the values during insert.
At query execution time IDAA returns the QRYDTA for the REAL columns as double values in the DRDA message flow, however the DRDA client (receiver makes it right) would convert the result back to single precision REAL values on the mainframe or on the client.
So the only thing the customer would have to do is to switch on the new behavior on the IDAA server.
Disadvantage: 1) 4 bytes more space used on Netezza per REAL column (this may be a problem if very wide tables already use up to the max space of 32K bytes per row)
2) CPU cost for the conversion on the DRDA client from double to real (DRDA receiver makes right) - e.g. if they are running local query applications on z/OS the conversion cost for the query result is on z/OS side
Do not place IBM confidential, company confidential, or personal information into any field.