"Lucy, 'splain me!" (Security Question)

[DAsmussen@xxxxxxx]

OK Folks,

I'm obviously overlooking something here, so perhaps someone out there can
point me in the right direction.  I have a user profile defined as user class
*SECOFR, with *ALLOBJ special authority (among others) on a CISC system
running V3R2 of OS/400.  Suddenly, perhaps after a PTF application, this user
profile can no longer perform CHGUSRPRF or WRKDIRE -- it gets a "*SECADM
special authority required" message for both functions.  As far as I can
tell, both commands are still at the same factory default authority settings
that they were when this profile _WAS_ able to perform these functions.

Under the old V2 releases, a profile like this could have changed the QSECOFR
password.  So what gives?

TIA,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"Experience is the one thing you have plenty of when you're too old to get
the job." -- Unknown
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---