This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.
See this idea on ideas.ibm.com
Have a sign on that is used by multiple users. Is used by our ERP software Infor XA. User has no maintenance capabilities, only review. Would like to exclude user from the QMAXSIGN system value. Similar to the Password Expiration Interval that can be overridden with *NOMAX.
Our global setting is set to 5 unsuccessful attempts before a user is disabled. We would like to be able to exclude a single user from this global setting so that regardless of the number of attempts the user id does not get disabled.
Idea priority | Medium |
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.
Hi,
We have come up with a successful workaround that uses the STRWCH function to monitor for this and re-enable the user.
Whilst I agree it's more or a hassle than the fix you have requested, we added the extra function to the watch program that retrieves the job and IP address details of the session that disabled the user and sends this detail to the SysAdmin in an email before automatically re-enabling the disabled user.
This is a duplicate of http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=118931.