Let me guess, 27 people know the password for QSECOFR. When you change
that password someone screws it up and disables that account. Effectively
doing a Denial Of Service attack against QSECOFR. So you are trying to
prevent this DOS attack.
This fear of a DOS attack against your security accounts is why some
people only have QMAXSGNACN vary off the device and not disable the user
profile.
Of course, I feel your pain. But, expect someone to reply that your
security accounts should be the ones which get disabled the fastest upon
incorrect sign on. They have a point also.
Or, instead of QSECOFR, you have a 'generic' account for shop floor
personnel or some such department?
For that case, the message monitoring is probably the desired solution.
Rob Berendt
This mailing list archive is Copyright 1997-2026 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.