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.
email@example.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Ideally also timestamp support inside common language as RPG should be considered.
i.e. %TIMESTAMP(*UTC) return current timestamp in UTC
nowadays one have to convert using an OS API.
It's ok, but ideally should be more idiomatic: for example when one call and external REST service is usually customary to send a timestamp "on the wire" for the operation; it is better to have then a string representing the timestamp with full timezone offset info or Z if *UTC.
Ideally the TIMESTAMP type should be timezone aware in the RPG language.
%CHAR(mytimestamp) should return a timestamp ISO string including the time zone if one wishes.
This would provide a unified clean solution for a system that talks to systems using different timezones or clients.
in place of the CHGJOB, maybe a new PARM in the JOBD object that would define the timezone
The Anydate function is not a complete solution, since it does not have a hook in timestamps accessed directly with the MI. However the coverage is pretty good, and may be adequate for many applications.