This is my thoughts exactly... I was going to try to automate with a delay of 20 minutes - would that be incentive enough? Who knows.
The real issue is with users of "wearable" RF devices that have a limited keyboard. They are limited to one option on one menu and *SIGNOFF in their profile. We printed barcodes for their passwords so they could simply scan it. You would think that would be enough... but even that seems to be difficult (rolling my eyes).
We have exit point software in place - I could easily limit a function or command by user or group profile.
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin Bucknum
Sent: Tuesday, November 2, 2021 9:38 AM
Subject: Re: Enable Disabled Users and Devices
It should be pretty easy to write something that finds the disabled profiles and re enable them. You've seen the disabled user id query that K Crawford sent, that gives a lot of info, but for your case, you may want to look at qsys2.user_info. It should have everything you need for identifying the users. For devices, not sure.
Just a thought. For me, I would be wary of something that automatically renables user profiles. It will create (at least for us) another report that must be checked every day. If your users have command line access, this is what I would do.
Create a command and cl/rpg that just takes a user profile (or devd). Command processor has an owner with proper authority, and you adopt authority. It also does some logging, and sends a break message to somewhere monitored. Make the command and processing program *PUBLIC *EXCLUDE, put everyone that you trust to run the command into a group profile, and give them access to the command/processor.
If it is happening enough that you expect reports everyday, then just flat out automating it would work, but you really need to fix the user problem and not just through a bandaid over it. If it's not, then certain users have the ability to fix it for other users without involving IT, but you still get a notice when it is happening, and you can address repeat offenders as necessary.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.