This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
IBM does not intend to provide a solution to this request at this time, so it is being closed.
IBM's position is that allowing implicit conversion between Timestamp values and Date or Time values would not improve the clarity or maintainability of the RPG code.
If the table is defined using DDL, wouldn't you be able to set the relevant columns to default to CURRENT DATE/TIME/TIMESTAMP and not include them in the RPG at all? The column would be updated correctly at write time and fully accessible for read/update. The reason I suggest this is because I thought IBM was recommending against DDS over DDL for physicals & logicals, which is what we've been trying to do.
There are pro's and cons on automatic type casting... it saves you the %Date function (but is this such a major issue ?), but on the other hand you're not warned if you loose the time information (maybe it wasn't intended).