That's probably it because the directions were very specific about that :-)
And we actually had consultants in (won't name them but part of the name was
"As the _____ flies" or the bands "Counting ______" or Black ________") that
told my boss we needed to a GRTOBJAUT OBJ(*all/*ALL) OBJTYPE(*ALL)
USER(QSECOFR) AUT(*ALL).
Their "lead guy" came to me a asked me to do this and I reacted with a "Are
you kidding ? WHY ? !" he said they needed it done because they were having
problems with some of their programs. I told him they needed to figure those
problems out and this was not the answer and offered to help them trouble
shoot. He left and a couple of minutes latter my boss comes into my office
and said to do it. I explained to him why it was not a good idea and what I
had told this other guy. He went to them and came back and told me to do it.
I said that I needed him to sign off on it and he did. Unreal.
Chuck
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Tuesday, April 01, 2008 3:41 PM
To: Midrange Systems Technical Discussion
Subject: Re: Anti-virus for i5OS
Chuck Lewis wrote:
Joe,
Wasn't SSA one of the ones requiring QSECOFR for BPCS and then every 3rd
party add on package to BPCS did the same thing ?
And there was no way around that if you wanted to install it.
NOT saying your were responsible for that :-)
There was nothing in BPCS that required QSECOFR. As Charles points out,
it was primarily laziness on the part of the packaging team. If I
remember correctly, it was too much work to figure out exactly which
commands were needed. I think the final justification was that since
the installation did saves and restores, and *SAVRST was pretty close to
*SECOFR, may as well just require QSECOFR <grin>.
Joe
midrange.com
