|
Messages are logged to QSYSOPR and/or QSYSMSG for account lockouts. You can monitor these message queues and take the appropriate action which should include notifying management and logging the occurrence. Chris Bipes -----Original Message----- I have a requirement to prevent certain service/connection accounts from being locked out - for example due to password validation errors. This is to prevent the profiles being deliberately locked out as part of a denial of service attack. We do not want to set QMAXSIGN to *NOMAX as this applies at a system, rather than an individual profile level. Does anyone know of a way to do this? Is there an exit point we can hook into when a user profile is disabled and use this either to stop the profile from being disabled or re-enable the profile? Is there a way to override this system value at an individual user profile level?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
