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.
I live in South Africa, support customers in the UK, running an American operating system.
HLIST of a migrated dataset displays both the migration date and the last reference date.
However, both these dates have the format xx/yy/zz, with no explanation as which is the day, month, year.
In my case, a dataset has a migration date of 09/07/02
In America, this would be interpreted as 7th September 2002
In the UK, it would be interpreted as meaning 9th July 2002
In South Africa, it would be interpreted as 2nd July 2009
Which of these 3 interpretations is the correct one ??
It would make it a little easier if the year were 4 digits.
But then you still have the difference between US (mm/dd) and the UK (dd/mm)
Why not use either the ISO standard of 2023-04-17 or the very unambiguous 17-Apr-2023
To cater for US preferences, you could even make it Apr-17-2023
P.S. I choose a dash instead of a slash because it makes the date easier to read instantaneously.
P.S. 2-digit years went out at least 23 years ago.
Idea priority | Low |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.