Authority Restoration During an Upgrade (6.1 -> 7.2)

[Terry Wincheste]

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

Terry

Note: I also posted the the MidRange mailing list...but didn't see it come thru...not sure why.

[john.sev99]

I don't think a RSTAUT would have done anything. The OS upgrade would replace objects in QSYS (and other places of course) and when that happens, authorities aren't retained and as such I believe the private authority information would be removed from the profile. We have some programs we run after an upgrade to restore any customisations and we manually maintain the information.
I'm thinking that if you restore the user profile from a save taken before the upgrade (SAVSYS or SAVSECDTA), running the RSTAUT after that would restore the private authorities?