Since you did not RSTUSRPRF *ALL the RSTAUT would not have done anything
anyway, I suspect you problem lies elsewhere. The method of upgrade is
irrelevant in this case.
It sounds like a profile has private authorities to commands in QSYS. Since
those objects are replaced during the upgrade the private authorities
clearly would not be there any longer since the object is gone (replaced).
You'll need to get the script used in the installation to set those
authorities and re-run that part of the installation.
I won't even start on the lack of wisdom in doing what the vendor apparently
did. I was taught a phrase long ago: "Ignorance can be fixed, stupid is
forever". The vendor was stupid, therefore assuming the ability to do so,
find another vendor.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Winchester Terry
Sent: Friday, May 25, 2018 10:11 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Authority Restoration During an Upgrade (6.1 -> 7.2)
We recently upgraded our Test system LPAR from V6R1 to V7R2.
Everything seemed to have worked fine with the exception of one software
package. It was failing for security reasons...then we discovered that a
generic profile it uses had access to many QSYS objects/commands.
We didn't see anything in the upgrade guide indicating that a RSTAUT was
needed nor could we find anything security-related that was missed during
the upgrade. We performed the upgrade using the DVD optical
drive...disk-by-disk.
I am thinking that if we had done a RSTAUT at the end of the upgrade (but
before a SAVSYS) that we might have avoided this problem. OTOH, I'm not sure
where the RSTAUT would get its information from if we didn't restore user
profiles from a prior backup.
Dummy me...I thought we might be able to do a SAVSECDTA to a *SAVF and then
use that to do a RSTAUT...but that does not appear to be a viable method.
Anyway, before we begin to think about upgrading our Production LPAR...I was
hoping someone might have some thoughts about where we went wrong -or- what
we should have done different.
Thanks for any input :)
----------------------------------------------------------------------
Confidentiality Notice: The preceding e-mail message (including any
attachments) contains information that may be confidential, protected by
applicable legal privileges, or constitute non-public information. It is
intended to be conveyed only to the designated recipient(s). If you are not
an intended recipient of this message, please notify the sender by replying
to this message and then delete it from your system. Use, dissemination,
distribution or reproduction of this message by unintended recipients is not
authorized and may be unlawful.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
