One option is to use the 'profile handle' APIs. It would try to get a get
a handle on this user profile.
Another option is to DSPUSRPRF to an output file. Here's the cool part.
On this output file do this:
ADDPFCST FILE(ROB/USERLIST) TYPE(*PRIKEY) KEY(UPUPRF)
Now that file has a key on the table by user profile. Ever write an RPG
program? You can chain on that user profile and see if it is disabled.
(See column UPSTAT.)
Now you can trap on this and shoot off an email or some other corrective
action.
Put this program on the job scheduler and away you go.
Rob Berendt
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.