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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team 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.
Receive a notification on the decision
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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
We are using IBM's MFA for z/OS solution to MFA enable our systems administrators across a wide range of interfaces including TSO, CICS, DB2, IMS, Netview, Omegamon, and zWAS.
Since we are using a compound in-band solution where the password and MFA code are passed together as a single string delimited by a separator, the application presents this longer password to RACF in the normal way, the MFA software handles parsing out the code and validating this with the appropriate backend system. This makes it largely transparent to the application.
Note we are able to use admin console without issue with this MFA set-up i.e. using password%mfacode
So any command syntax is essentially the same , it's still a username and password.
The issue is that the credentials passed to the syncNode.sh script are being used internally multiple times (they do succeed once), which leads to the syncNode.sh failure since the MFA code is one time use only.
Please see IBM Case TS004134896 for detailed documentation of the use case failure.
Do not place IBM confidential, company confidential, or personal information into any field.