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 posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
Get feedback from the IBM team to refine your idea
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
IBM Unified Ideas Portal - https://ideas.ibm.com/ - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
Thanks for bringing the difficulties of the date format to our attention. We would like to improve this design, so we are changing the status of this RFE to Uncommitted Candidate as we look into potential solutions.
In order to avoid doing this much manually, I hope the workaround described below will help you until the RFE is delivered.
When working with CBU keys I download them in a document
1. Open the document
2. Cut and paste every thing to ACS RSS
3. Scan and replace ADD in CL:ADD
4. Scan and replace VNDDTA(*NONE) in VNDDTA(*NONE);
5. Scan and replace 2022-11-25 in '2022-11-25'
In most cases the keys need to be downloaded to other LPARS with RSS that is easy.
If the CBU system is a "COLD" target LPAR, I do one thing extra.
I scan and replace SERIAL(*LOCAL) by SERIAL()
Afterwards I add the keys to my "WARM" source LPAR.
Hope this helps you through that time ;-)
Couldn't agree more. The implementation of *ISO with the keys means I always need to cut/paste and then carefully go into each ADDLICKEY command and correct the date to *JOB format.
Perhaps another solution would be to change the CL command paramater TYPE(*DATE) to accept both *JOB an *ISO formats?
If ESS could output the keys in *LICKEYFILE format, or a CVS format that could be easily uploaded from a Mac or PC to a *LICKEYFILE, then one can apply the keys in one fell swoop with ADDLICKEY LICKEYINP(*LICKEYFILE), and not depend on the ItNoWorkie Java app to download directly to the system.