This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
However, our callable services use the Lilian format. Would you be looking for similar callable services that use Epoch time instead of a Lilian date?
Note that callable services are not supported for AMODE64 applications.
I was also curious if you've experimented with interlanguage calls as a solution to this issue? One way that this problem could be solved today is by making a call to the time() C function from COBOL.
https://www.ibm.com/docs/en/zos/3.2.0?topic=applications-communicating-between-c-cobol
https://www.ibm.com/docs/en/zos/3.2.0?topic=functions-timetime64-determine-current-utc-time