RE: Rename WRKUSRPRF

Once upon a time we were in the middle of a hectic series of program changes. Word came down from on high that Programmers were to be given free access to the production libraries.

My boss objected as much as he could, then got the edict in writing.

Of course it was a zoo! We only had a home-grown change management system at the time, that was totally bypassed. Multiple programmers changing the same program at the same time, and placing their copy in production one after the other, wiping out each other's changes! Etc. Etc.

Get any edicts and decrees in writing (preferably on paper outside the email system). Make sure you have a copy outside the system!

Write some daily jobs that un-do the changes you fear (ie switch the programmers and users back to *PGMR and *USER classes).

Then sit back and watch the fun!

Oh-- keep your resume up-to-date!

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Rich
Sent: Tuesday, August 29, 2017 4:02 PM
To: midrange-l <midrange-l@xxxxxxxxxxxx>
Subject: Rename WRKUSRPRF

For reasons beyond my control or influence, a user on a system has been
granted QSECOFR authority. We're concerned about a number of problems
with that, but mostly the use (abuse) of the WRKUSRPRF command.

Are there problems with renaming QSYS/WRKUSRPRF? Can I simply RNMOBJ
OBJ(QSYS/WRKUSRPRF) OBJTYPE(*CMD) NEWOBJ(NEWUSRPRF) and still be ok?

James Rich