IBM Z Software
This portal is to open public enhancement requests against IBM Z Software 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.
Hi,
In IZSAM 8.3 we have added GA dates to as many products as we could find. IBM of course is more comprehensive but BMC and Broadcom are also represented. As for other ISV's if the data is publiclity available the data can be added to the GKB. The same applies to EOS dates for ISV's. If it's publicly available we can add the EOS dates.
Regards
Jim K.
Hi, would be possible to add GA dates?
Can you consider adding EOS dates for ISV SW too (currently only displayed for IBM SW and few other vendors)?
Thanks,
Khalid
Hi Ales,
Ok now I know it was not the Asset version field you were interested in and also why you want to do this. It's not possible to do what you want as that field contains varios data apart from VRM. There is also RSU levels for IBM software and other levels for ISV software. In reflection years ago when the database was first designed, we maybe needed to have different fields to hold this data but alas it's not practical to do that now.
Regards
Jim K
Hi Jim,
"Asset Version" column prefixed by "V" is not the field I have on my mind as it does not contain such granular information (like z/OS V2 does not give a clue which release is actually used) but I am referring to "release" column (2.4.0 for z/OS already provides needed info.. but often this is string - mix of characters, prefixed by R, hexadecimal value etc.). Having this field in NUM format makes reporting data processed by excel much easier (in pivot show the products, see where they are installed and in which version - MAX or MIN depending on the purpose of the report and set conditional formatting to highlight products which needs attention - are close to EOS, compatibility requirements with other products etc.). I created myself a mapping table to bypass this to link reported release ie. 5.2.7 (string) like 5.27 (number) but it's needed to maintain such table manually as any "new" release appears. Hope it's a bit understandable what I tried to achieve ;-)
Thanks a lot for pointing me to EOS report in Discovery tab, I will check that.
Regards,
Ales
Hi,
Not sure I understand the first part of the RFE regarding numerics. In the Asset reports all versions are prefixed with a V. This was part of the original spec for the 7.2 release and has not changed since then.
As for EOS dates, there is an EOS report in the Discovery tab that will give you the information you have requested.
Regards
Jim K.