|
[ Converted text/html to text/plain ] You should be able to write a break handling program that would monitor for certain messages and then perform specified functions. It could be possible to write it in RPG but I think CL would be better. Thanks Dennis Nel -----Original Message----- From: Chuck Lewis [mailto:clewis@iquest.net[1]] Sent: 20 September 2001 04:01 To: midrange-l@midrange.com Subject: RE: Monitoring for a disabled user profile Nathan, I've setup QSYSMSG message queue and the system will send critical system messages to this queue. This includes disk messages, invalid signon attempts varying a device off, etc. If trying to signon with a disabled profile sends a message I would think it would go to this queue, but I am not sure it does. I could test it at work tomorrow. Then I have a program that reads QSYSMSG on a very regular basis and depending on the message, sends alerts to certain personnel. It could automatically reenabled a profile with a minor mod... Chuck P.S. You a native "down under" ? I knew a Matt Simpson that worked for IBM here in Indianapolis at one time... -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com[2]]On Behalf Of Nathan Simpson Sent: Wednesday, September 19, 2001 8:58 PM To: MIDRANGE-L@midrange.com Subject: Monitoring for a disabled user profile Hi, Is it possible to monitor for when a user profile becomes disabled and then automatically run a command which will re-enable the password? I only want to run this command for when one particular user profile becomes disabled. TIA Nathan Simpson _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l[3] or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l[4]. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l[5] or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l[6]. ===References:=== 1. mailto:clewis@iquest.net 2. mailto:midrange-l-admin@midrange.com 3. http://lists.midrange.com/cgi-bin/listinfo/midrange-l 4. http://archive.midrange.com/midrange-l 5. http://lists.midrange.com/cgi-bin/listinfo/midrange-l 6. http://archive.midrange.com/midrange-l
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.