I agree - but keep a copy of any documentation and any e-mails (with their replies)
This happened to me some years ago - and when that QSECOFR person screwed up (it was a doozy) - I was ripped a new one - until I showed them everything that I had sent to upper management - with their replies
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, August 29, 2017 4:20 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Rename WRKUSRPRF
If such a user has *SECADM authority, and you can prove that he changed the user to up their authority, and management doesn't put a stop to it then you need to accept it as it is.
You've done your duty. Management won't do theirs. Cash the paycheck and move on to the next item on your task list.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: James Rich <james@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/29/2017 04:15 PM
Subject: RE: Rename WRKUSRPRF
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
On Tue, 29 Aug 2017, Steve Pitcher wrote:
You can put some exit programs in place to prevent actions. But then the
person could remove those programs. Or they could use your copied
command. I'd be more concerned with them using the PWRDWNSYS command. Or
ENDSBS. Or DLTLIB. And so on.
The end game would be to show the powers that be how dangerous special
authorities can be and try to remove the excess authority rather than
playing Spy Vs Spy over and over again.
I completely agree. This exact battle has already been fought and lost.
The only good option I have left is simply to be a better spy.
James Rich
midrange.com
