Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
RFE Review. Thank you for raising this RFE and apologies for the length of time it has been in Submitted status. We agree that improving our provision for timestamps would enhance the product's capabilities. Currently, the ESQL TIMESTAMP datatype does not carry timezone information, and when they are created we use the FORMAT string to apply the timezone in the input data so that we end up with either a TIMESTAMP (reflecting local timezone) or GMTTIMESTAMP (reflecting the GMT timezone). This means that currently when we come to CAST a timezone back to CHAR data on the wire, we don't have any way to express a "particular desired output timezone". There is a current workaround for this situation in that in some of our parser domains, the message tree field carries timezone information such that we can preserve it if a message tree field survives from input to output. This is controlled by settings on XMLNSC. ESQL has options not to include the timezone on a CAST just in case the message tree field is carrying the information for it. If / when implementing this in a future release, we would need to update the underlying message tree field value types to carry a timezone and then update the parsers/writers to look for it. This has a high test cost for us, and hence why this has not yet been prioritized for inclusion in the product. That said, we approve of the idea and will continue to monitor the idea for popularity. Status of the RFE is updated to Uncommitted Candidate.