Security issues going from V5R2 to V5r4

5 pts.
iSeries security
iseries v5r4
we upgraded from V5R2 to V5r4 and now I am getting authority problems on any update programs in our custom programing library. User authorities were copied over. That seems fine. Were there any know security problems going from R2 to R4? I get around each instance by changing program to use Adopted authority of the program owner but feel this is a bandaid and would like to find root of the problem.

Software/Hardware used:
Migrated from 720 on V5R2 to I5 model 520 running V5R4

Answer Wiki

Thanks. We'll let you know when a new response is added.

You should look at the iSeries Backup and Recovery book and look at Chapter 14 on the “Previous Release-to-Current Release Support” section. I always refer to this section when I move a client up to a newer system. I believe that you might resolve your problems by using the RSTAUT command but you should read the help text before you issue the command.

Discuss This Question: 2  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TomLiotta
    This apparently wasn't an upgrade -- it was a migration from a system at V5R2 to a new system at V5R4. An upgrade can be fairly simple. A migration can have numerous problems if the steps are done in the wrong order or at the wrong times. Please describe the steps that you took. How did you save security information on the V5R2 box? How (and when) did you restore profiles and restore authorities on the V5R4 system? In general, there shouldn't be an issue going from V5R2 to V5R4. But issues can easily be created. Tom
    125,585 pointsBadges:
  • Lovemyi
    If the problem was only in your custom library objects then there might have been a command in QSYS that was changed and overwritten back to the standard that use to adopt authority before the program that get calls runs so that jobs going through the batch jobq might not have the right authority once the job is submitted. We had this problem with an upgrade from V5R2 to V5R3 and only on batch jobs from our custom system. We copied the SBMJOB command to a library first in the system portion of the library and then the copied command was changed to use routing data of *JOBD instead of QCMDB as the default. Then everything worked normal. Could it be something like this? There were other things with routing data that was set up years before I came to work here and this was one item that was not done using the proper addage that you never never never change anything in the OS directly or risk that it gets removed during an upgrade. Hope this helps give you food for thought. Lovemyi
    2,310 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: